DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22151>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22151 ThreadPool OutOfMemoryException [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-08-06 16:39 ------- Well, it seems to me that the ThreadPool shouldn't die when the JVM is out of memory. In my case, the JVM hasn't been allocated all of the memory it can be, so future attempts to create new threads would be likely to work. Would it be too hard to catch this exception and make ThreadPool sleep for a few seconds? I'll try to hack up the code and see what happens. For now, I'll close this bug as it's being received with attitude. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
