I have a
JSF application running on WAS 6.1 server running on iseries V5R4
The WAS is running on separate memory pool. The memory allotted to the pool is 4GB. The maximum eligible
thread count for the WAS pool is given as 500.
Recently I converted my JVM to IBM 32 bit from classic JVM.
In the new environment I gave the max heap size as 2000 MB and initial heap size as 96 MB.
I used jmeter scripts to create a load
testing.
Usually in my production, in the WASserver(WAS61SVR) job I can see no: of threads in the range of 700 to 900.
Some times the thread count goes beyond 1000. In production the WAS6.1 is running on base pool.
But when I�m testing in development server, when I create 990 threads, the JVM heap reaches 2048 MB and used memory is in the range 1600-1700 MB.
The application works fine in this case.
When the thread count crosses 1000, the WAS6.1 server is shutting down. The heap is the manageable range of 1600-1700 MB even with 999 threads.
I repeated the test scenario couple of times, each time when the thread count crosses 1000 the application server shuts down.
Is there any upper count for the number threads for WAS 6.1 server or memory pool which hold WAS server?
Please help.