This lets me think of the following scenario:
If you actually reach the thread limit of 1024, which the error message
"OutOfMemory: unable to create new native thread" indicates, the your threads
consume 1024 * 1024k of memory for the per process stack.
I.e. in addition to the heap of 1024MByte
anonymous wrote : OutOfMemory: unable to create new native thread.
This error is actually not necessarily related to lack of memory. It basically
means that the JVM could not create a new thread of execution as requested.
I have only ever seen it in relation to the Linux kernel 2.4's (and earlie
We have been playing around with the parameters that I explained before.
We changed Xms to 1024m and after several hours running with these setting, we
obtained this:
java.lang.OutOfMemoryError: unable to create new native thread
Then we decided to reduce Xmx to 1024m instead of 1536 and Xms to
In the first quick browse, I noticed that parallel GC does not make much sense
with just 2 processors. It may even slow down things a bit. Use it if you have
4 procs or more.
But this is not the cause of your problem.
In addition, the per thread stack size (-Xss:1024k) seems quite big. How many
