Are you running on 32-bit or 64-bit JVM on OS X 10.5.2?
If you are running java without -d64, it would be running 32-bit by
default.
Typicaly around 2000 or so is the thread number limit on 32-bit
process due to its virtual address space limit (1 thread may claim 1MB
of virtual space for stack). Running java with -d64 will invoke 64-bit
JVM on leopard, and should increase the threads limit accordingly.
The actual physical heap space is different story. It needs to
increase only if you app/thread really use/allocate memory.
But I am wondering why Tiger server did not have the issue. AFAIK, 64-
bit JVM is only available on Leopard.
Yong
On 3-Apr-08, at 7:49 AM, Stephen Caine wrote:
List members:
I have a process that generates hundreds of threads. Running on Mac
OS X 10.5.2 Server, the thread count tops out at approximately
2500. After which, the process is terminated. The heap size is set
to 1 gigabyte. My question is how to increase the capacity of the
JVM to handle more threads. Is the value of 2500 an absolute limit,
or can it be modified by setting the thread allocation, increasing
heap size or the use of another java option?
As an aside, this issue did not occur with Mac OS X 10.4 Server.
If you have time, what causes a process to generate threads?
Any advice will be appreciated.
Stephen Caine
Soft Breeze Systems, LLC
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
