java -Xmn and -Xmx options 1

[vkarthik]

I have a java application that runs on solaris and windows. Its started with java's -Xmn and -Xmx options, with values 64 MB and 128 MB respectively. On Windows, it is starting up with 20 MB, but on solaris, it starts up with a whopping 117 MB! And after a while, it reaches 180 MB, and goes down with OutOfMemory error. All this only on solaris and not on win2k.... The code is totally independent of the platform. Does any one have a clue what could be the reason?

Also, please help me understand what exactly the Xmn and Xmx options mean? Does this mean, there is a guarantee the max memory will not cross the value specified in Xmx?

Just an additional info, I used the 'top' command to monitor the mem on solaris. The virtual memory used for this process, during its startup is reported as 117 MB as I said.

This is very critical and urgent to me, so any help will be greatly appreciated.

LOL A ship is safe in the harbour, but that's not what it is meant for!!! LOL

 

[idarke]

This article makes a reference to your problem - it infers that the Solaris jvm is the culprit and you're stuck with it.

http://www.theinquirer.net/Default.aspx?article=7679

You may have to run with a larger heap size on Solaris to compensate for the jvm's inherent memory hogging...

 

[vkarthik]

You saved my day man! i cant tell u how useful this finding of urs is.... thanks a lot.

If you know of some good method to overcome this, can u suggest... You've already suggested increasing heap size.. can u tell me approximately by what proportion i can increase it with... with reference to the figures ive given above.

LOL A ship is safe in the harbour, but that's not what it is meant for!!! LOL