[ http://issues.apache.org/jira/browse/GERONIMO-585?page=all ]
Matt Hogstrom closed GERONIMO-585. ---------------------------------- Resolution: Fixed Assignee: Matt Hogstrom Applied patch...in the future we need a better mechanism but this patch alerts the user to the problem. > No indication when DefaultWorkManager pool is exhausted > ------------------------------------------------------- > > Key: GERONIMO-585 > URL: http://issues.apache.org/jira/browse/GERONIMO-585 > Project: Geronimo > Issue Type: Improvement > Components: connector > Affects Versions: 1.0-M3 > Reporter: Aaron Mulder > Assigned To: Matt Hogstrom > Fix For: 1.2 > > Attachments: WorkExecutorPoolImpl.patch > > > I created a connector that executes 8 long-running Work objects at startup > (DefaultWorkManager pool size = 10). If I deploy it twice, the second deploy > operation hangs, causing the deploy tool to hang as well (and in fact the > server hangs if you try to shut down and you have to kill -9 it). There's no > evidence what the problem is. It would be nice if we at least printed a > debug message or something when you submit work and there's no worker thread > available. In truth, there are better ways to code the RA, but the hangs, > and the fact that it hangs the deployer and server shutdown too... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira