geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-585) No indication when DefaultWorkManager pool is exhausted
Date Sun, 13 Feb 2005 16:34:12 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-585?page=history ]

Aaron Mulder updated GERONIMO-585:
----------------------------------

    Description: 
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...


  was:
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.  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 appearance of a hang,
and the fact that it hangs the deployer too...



> No indication when DefaultWorkManager pool is exhausted
> -------------------------------------------------------
>
>          Key: GERONIMO-585
>          URL: http://issues.apache.org/jira/browse/GERONIMO-585
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: connector
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder

>
> 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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message