I have an opportunity to resolve. We use the same install process for
all of our application servers. We load the op-sys (CentOS 6) using a
pxe-boot process and a standardized kickstart file.
So wouldn't you know, I have one server out of 10 on which we may not
create a java heap space the same as all the others. WTF??
Our standard test is java -Xmx2560M. On all systems but the one (that
the boss HAS to have!) this runs and generates a grocery list of
commentary. On the bad boy we get:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
The largest number we may use on this machine is java -Xmx1024M.
Now for some contradictory information. Yes, we build our applications
on the 32bit version of CentOS 6 (PAE). This particular instance (VM
guest) has 12GB of memory allocated to it and the VM host has 32GB, not
saturated.
Thoughts (besides slashing wrists)?
Howard
--
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
---
You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
