With 32-bit JVMs, the heap size limit is dependant on the OS/JVM
combination. It is less than 2^31 (less than 2gb as you are
experiencing) or less than 2^32 (less than 4gb).
You can use a 64-bit JVM (check in the docs if this is supported on
SuSE).
But maybe you should tell us why you need to increase the heap (lots
of caching or simply to take advantage of the memory upgrade?)
--AlexisMP
On 18 mai 08, at 03:32, glassfish_at_javadesktop.org wrote:
> We have successfully been running glassfish-v2ur1-b09d with
> jdk1.6.0_03 on suse enterprise linux for many months using the
> following JVM setting:
>
> <jvm-options>-Xmx1536m</jvm-options>
> <jvm-options>-Xms1536m</jvm-options>
> <jvm-options>-XX:MaxPermSize=192m</jvm-options>
>
> I have now tried to increase the memory to 3GB after a server upgrade:
>
> <jvm-options>-Xmx3072m</jvm-options>
> <jvm-options>-Xms3072m</jvm-options>
>
> Startup now fails with message:
>
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
>
> but the server has 13GB of free ram! Can anyone explain why this is
> happening?
>
> I have also tested with settings of 2048m with the same results.
> For some reason 1536m seems to be the maximum we can use.
>
> Many thanks in advance.
> Gerald
> [Message sent by forum member 'ggierer' (ggierer)]
>
> http://forums.java.net/jive/thread.jspa?messageID=275035
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>