Maxheapsize In jmap Output Does Not Match Xms Setting For OC4J Container.
Last updated on FEBRUARY 15, 2017
Applies to:Oracle Containers for J2EE - Version 10.1.2.3.0 and later
Information in this document applies to any platform.
Trying to monitor an OC4J instance memory usage in iAS 10.1.2.3 running JDK 1.4.2_14.
When running the command:
for this OC4J instance, the maxheapsize shows 64MB while the -Xmx parameter is set to 512M.
The jmap tool doesn't show 512M as expected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms