DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-08-06 01:03 --- Gave IBM JDK 1.4.1 a try and I'm having the same results unfortunately: Aug 5, 2003 8:56:51 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError: JVMCI015:OutOfMemoryError, cannot create anymore threads due to memory or resource constraints at java.lang.Thread.start(Native Method) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.init (ThreadPool.java:582) at org.apache.tomcat.util.threads.ThreadPool.openThreads (ThreadPool.java:460) at org.apache.tomcat.util.threads.ThreadPool.runIt(ThreadPool.java:293) at org.apache.tomcat.util.net.TcpWorkerThread.runIt (PoolTcpEndpoint.java:536) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:619) at java.lang.Thread.run(Thread.java:568) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-08-05 21:35 --- Actually, I did that already. Tried ulimit -s 2048 and it had no effect. I wouldn't have posted this here if I hadn't exhausted myself, google, and tomcat- user already. I know better than that :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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 --- Additional Comments From [EMAIL PROTECTED] 2003-08-05 21:06 --- I forgot to note that this error can be reproduced 100% of the time. I rebooted the server dozens of times and it kept happening. Although, it does not seem to fail consistently at the same point. When that error hit catalina.out the JVM had anywhere between 160 MB and 220 MB of memory allocated to it. The only way I got it working was to leave -Xmx at less than 1 GB of memory. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-05 21:10 --- Use tomcat-user to debug and look at ulimit command. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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 --- Additional Comments From [EMAIL PROTECTED] 2003-08-06 08:38 --- Perhaps a silly question, but have you tried to run Tomcat on its own without your own code deployed? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-05 21:52 --- I urge you to try the IBM 1.4.0 VM. I have recently helped put in production a 4 CPU server with it (with Coyote HTTP/1.1), and it seemed to work very well. Definitely, I didn't see any issues on startup. Forget about the Sun VM on Linux IMO (the client JIT is slow, and the server JIT uses way too much memory, with questionable reliability). That being said, you're filing a bug about Tomcat here, so you should try to isolate a problem with that (and I don't see how a bug triggered by -Xmx could be caused by Tomcat). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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 --- Additional Comments From [EMAIL PROTECTED] 2003-08-05 22:22 --- I agree with what you said, trying another JVM would definately help to isolate the problem. I'll give the IBM JVM a try and go from there. That's better than all zero of my alternative ideas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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 --- Additional Comments From [EMAIL PROTECTED] 2003-08-06 16:44 --- It really looks like a kernel/system config issue. OutOfMemory errors are the worst descriptive errors from java because they may be thrown even if there is plenty of memory left. (At least on another Unix platform) http://jakarta.apache.org/tomcat/faq/memory.html#why - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22151] - ThreadPool OutOfMemoryException
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 --- Additional Comments From [EMAIL PROTECTED] 2003-08-06 07:12 --- You can keep your bug open if it makes you happy, but I cannot do anything to fix it, as it doesn't look like a Tomcat issue. Maybe the cause is indeed that it can't create more threads ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
