The tomcat-sso server log from that run shows an OOME during shutdown:
2008-10-16 15:44:51,404 DEBUG
[org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer]
(JBoss Shutdown Hook) Undeploying
AbstractVFSDeploymentContext@21974138{vfsfile:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso/deploy/ejb3-interceptors-aop.xml}
AOPDeployment@174be7{name=null installed=false beanFactories=[]}
2008-10-16 15:44:52,071 WARN
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (JBoss
Shutdown Hook) Error uninstalling from Described:
name=ai03q-vnd9ln-fmdsu685-1-fmdsuovw-3o state=Described
java.lang.OutOfMemoryError: Java heap space
This happens early in the shutdown, so it's not unreasonable to think
the heap was nearly full during the failed startup.
The tomcat-sso config is set w/ a lower memory max than most:
<jvmarg value="-Xmx128m" />
<jvmarg value="-XX:MaxPermSize=512m" />
A few days ago the jrmp-invoker server also failed to start w/ an OOME
on a local test. It too had -Xmx128m (since changed).
Looks like our minimum memory usage has grown.
Dimitris Andreadis wrote:
It's been a few runs now that the tomcat-sso configuration
doesn't start
properly:
tomcat-sso-tests:
[echo] creating tomcat-sso config
[copy] Copying 374 files to
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso
[copy] Copied 73 empty directories to 2 empty directories under
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso
[echo] Overwriting config descriptors
[copy] Copying 4 files to
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso
[server:start] Starting server "tomcat-sso", with command (start timeout
is 120 seconds ): [server:start] /qa/tools/opt/jdk1.5.0_15/bin/java -cp
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/bin/run.jar:/qa/tools/opt/jdk1.5.0_15/lib/tools.jar
-Xmx128m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true
-Djava.endorsed.dirs=/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/lib/endorsed
org.jboss.Main -c tomcat-sso -b 10.18.94.175 -u 227.43.0.134
[server:start] Failed to start server "tomcat-sso" before timeout.
Destroying the process.
> From the log, I can't tell what's wrong:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Whoever is changing the tomcat configs can you please make sure the
tomcat testsuite configs are in synch?
Cheers
/D
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com