I've been successfully running EAP for several months now. Our IT department recently pushed an OS patch and now EAP does not start on the servers that have been patched. I'm waiting on details from the about what exactly was pushed. In the meantime, the biggest difference seems to be the JAVA patch level.
The configuration and error are shown here:
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms2048m -Xmx2048m -Xss128k -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true
CLASSPATH: /loc01/engtools/jboss/jboss-eap-5.1/jboss-as/bin/run.jar
=========================================================================
The stack size specified is too small, Specify at least 160k
Could not create the Java virtual machine.
These settings work fine on the servers running JAVA 1.6.0_33.
But on servers with JAVA 1.6.0_39, I get the error listed above and JBOSS does not start. To work around the problem, I've changed -Xss128k to -Xss194k. With that change, JBOSS starts up and functions fine. But the vendor of the EAR file JBOSS is hosting is complaining about that setting, claiming it's way too high and must be -Xss128k.
Does anyone have any insite to what the real problem might be? Is it really the JAVA patch version causing this? I'm trying to find documentation stating such, but to no avail.
Server configuration:
JBOSS EAP 5.1
LINUX REHL 5.8
Thanks for any suggestions!
1 of 1 people found this helpful