[
https://issues.jboss.org/browse/JBIDE-14819?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-14819.
---------------------------------
Resolution: Done
Purely internal additions with no clear way to replicate.
If using central or download runtimes or anything else which makes use of URLTransport
freezes the workspace, it may be related to this jira.
BarrierWaitJob.interruptableJoin can freeze if job completes before
listener is added
-------------------------------------------------------------------------------------
Key: JBIDE-14819
URL:
https://issues.jboss.org/browse/JBIDE-14819
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.1.0.Beta2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta2
Because the barrierWaitJob depends on adding a job listener to do its custom join, it is
possible that the job completes before the listener is added. Instead, the join() method
should optionally schedule the job itself, AFTER the listener is added.
This would ensure that there can never be a case where the job can be scheduled and
completed before the listener is added.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira