Deadlock due to UI updates from user threads
Snippet from thread dump of SoapUI Pro 4.5.2: Found one Java-level deadlock: ============================= "LogList Updater for script log": waiting to lock monitor 0x000000000fe86928 (obje...
Forum Discussion
Well, I'm not quite sure what I was doing inside SoapUI when the deadlock occurred. I didn't actively use it at all really, but i might have left a test case loop running (by the "Loop TestCase continuously" feature) when I last used SoapUI (a few hours before the deadlock occurred).
Either way, I think it is fairly obvious from the thread dump where the bug is (you are violating the general rule "All Swing components and related classes, unless otherwise documented, must be accessed on the event dispatching thread." mentioned in the javadocs I linked to).
I certainly agree that this may be hard to reproduce and test, but the fix is relatively easy - just use SwingUtilities.invokeLater() or something equivalent to call JTestRunLog.addText() from WsdlTestCaseDesktopPanel$InternalTestRunListener.beforeRun()
EDIT: Found a stackoverflow entry that you might find interesting: http://stackoverflow.com/questions/3014 ... at-runtime
Either way, I think it is fairly obvious from the thread dump where the bug is (you are violating the general rule "All Swing components and related classes, unless otherwise documented, must be accessed on the event dispatching thread." mentioned in the javadocs I linked to).
I certainly agree that this may be hard to reproduce and test, but the fix is relatively easy - just use SwingUtilities.invokeLater() or something equivalent to call JTestRunLog.addText() from WsdlTestCaseDesktopPanel$InternalTestRunListener.beforeRun()
EDIT: Found a stackoverflow entry that you might find interesting: http://stackoverflow.com/questions/3014 ... at-runtime