This content has been marked as final.
Show 3 replies
-
1. Re: Locking and the DeployersImpl.shutdown()
alesj Mar 19, 2008 10:11 AM (in response to adrian.brock)"adrian@jboss.org" wrote:
I'm going to remove this test.
Can you just comment it + a big TODO?
And I'll adjust it accordingly to the new behavior."adrian@jboss.org" wrote:
The test actually suffers from a race anyway.
The deployment threads (as written currently) could run after the shutdown thread gets the lock which means the test would fail.
The test is designed in such a way that threads that come after shutdown should fail.
But yeah, I need to look into that race anyway. -
2. Re: Locking and the DeployersImpl.shutdown()
adrian.brock Mar 19, 2008 10:13 AM (in response to adrian.brock)"alesj" wrote:
"adrian@jboss.org" wrote:
I'm going to remove this test.
Can you just comment it + a big TODO?
And I'll adjust it accordingly to the new behavior.
You can find in the code in svn history there no need to comment out code.
If you want a TODO, JIRA with its scheduling mechanism are the best way
to make sure things don't get lost/forgotten. ;-) -
3. Re: Locking and the DeployersImpl.shutdown()
alesj Mar 19, 2008 10:16 AM (in response to adrian.brock)"adrian@jboss.org" wrote:
If you want a TODO, JIRA with its scheduling mechanism are the best way
to make sure things don't get lost/forgotten. ;-)
OK, a JIRA then. :-)