geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishnakumar B (JIRA)" <>
Subject [jira] Updated: (GERONIMO-585) No indication when DefaultWorkManager pool is exhausted
Date Wed, 01 Feb 2006 05:07:33 GMT
     [ ]

Krishnakumar B updated GERONIMO-585:

    Attachment: WorkExecutorPoolImpl.patch

Prints WARN message in log file WARN  [WorkExecutorPoolImpl] Pool size is fully consumed -->
Maximum Pool Size is :10

> No indication when DefaultWorkManager pool is exhausted
> -------------------------------------------------------
>          Key: GERONIMO-585
>          URL:
>      Project: Geronimo
>         Type: Improvement
>   Components: connector
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>      Fix For: 1.1
>  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:
For more information on JIRA, see:

View raw message