Yeah, Shawn, but you, like, know something about Tomcat and actually provide useful advice ;)
On Mon, Aug 8, 2016 at 6:44 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 8/7/2016 6:53 PM, Tim Chen wrote: >> Exception in thread "http-bio-8983-exec-6571" java.lang.OutOfMemoryError: >> unable to create new native thread >> at java.lang.Thread.start0(Native Method) >> at java.lang.Thread.start(Thread.java:714) >> at >> java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) >> at >> java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1017) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1163) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at >> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) >> at java.lang.Thread.run(Thread.java:745) > > I find myself chasing Erick once again. :) Supplementing what he told you: > > There are two things that might be happening here. > > 1) The Tomcat setting "maxThreads" may limiting the number of threads. > This defaults to 200, and should be increased to 10000. The specific > error doesn't sound like an application limit, though -- it acts more > like Java itself can't create the thread. If you have already adjusted > maxThreads, then it's more likely to be the second option: > > 2) The operating system may be imposing a limit on the number of > processes/threads a user is allowed to start. On Linux systems, this is > typically 1024. For other operating systems, I am not sure what the > default limit is. > > Thanks, > Shawn >
