cancel
Showing results for 
Search instead for 
Did you mean: 

shrinking jlaunch process

Former Member
0 Kudos

Hello All,

We have the following settings for heap on our EP6 J2EE servers...

Max Heap Size: 1024

-Xms1024m

-XX:NewSize=170m

-XX:MaxNewSize=170m

-XX:PermSize=192m

-XX:MaxPermSize=192m

-XX:+UseParNewGC

...

We are running on WIN2003 with 2.5 GB of memory and Java Runtime 1.4.2_08.

Checking the memory usage of the server jlauch process in Task Manager we see it take up approx 1GB after startup.

However, after a while of not being used, this memory starts to shink and we have seen it go as low as 500MB.

Then when a request is sent to this server, memory has to be reclaimed which causes a large delay (measured in minutes) for the server to respond.

Does anyone know of a way of preventing the jlaunch process from releasing the memory (I thought -Xms was supposed to do this)?

thanks,

Colin

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

The memory shortage proved to be the issue

Former Member
0 Kudos

Hello colin,

It is interesting to know what caused it.

did you solve it ?

dimitry

Former Member
0 Kudos

Hi Dimitry,

Not yet, we think it may be related to the a memory shortage. We have 2 x 1GB Server processes plus a 50MB dispatcher running on WIN2003 with 2.5GB. We think that Windows may be forcing the Jlaunch to give up some of it's memory for it's own use.

To test this theory, we are running with one of the Server processes disabled to see if the other retains it's full 1GB allocation, so far it has.

regards,

Colin