defining xmx 2560m and more on jboss as 7.1.1 gives wrong values in mangement console

mandarv99 Oct 16, 2013 7:24 AM

When I start Jboss as 7.1.1 on Windows 64 bit machine having RAM 4GB and specify xmx value greater than 2560 MB the management console gives wrong values. Heap Usage Max is shown in negative. Non heap usage and thread usage values are blank.

I have tried this with JDK 1.6 update 35 and JDK 1.7 update 4. I found same behavior on Linux machine having 12 GB ram. Is there any such limitation? The attached image is captured from linux server having following jvm settings. JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=1024m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"

1. Re: defining xmx 2560m and more on jboss as 7.1.1 gives wrong values in mangement console

ctomc Oct 16, 2013 7:36 AM (in response to mandarv99)

I think this was fixed in later versions.

Can you try with WildFly 8 beta1 which is the latest.

It should also be fixed in 7.2
Actions
2. Re: defining xmx 2560m and more on jboss as 7.1.1 gives wrong values in mangement console

wdfink Oct 16, 2013 8:50 AM (in response to mandarv99)

This is a calculation problem in the console. You might use the CLI command
/core-service=platform-mbean/type=memory:read-resource(recursive=true,include-runtime=true)
Actions

Go to original post