[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated JBAS-9037: -------------------------------- Attachment: jstack -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated JBAS-9037: -------------------------------- Attachment: (was: jstack) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] David Lloyd commented on JBAS-9037: ----------------------------------- We've been seeing sporadic hangs on various demo tests which may be related to surefire creating overlapping test instances, in other words a new VM is created before the old one terminates. Not sure if this is the same thing - look for a duplicate process. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Carlo de Wolf commented on JBAS-9037: ------------------------------------- I see Idea, maven (VM), surefire shell script, surefire (VM). So no overlapping process. {noformat} $ ps -ef|grep java carlo 16476 16450 11 13:45 ? 00:17:48 /usr/lib/jvm/java-6-sun//bin/java -Xms128m -Xmx1536m -XX:MaxPermSize=250m -ea -Xbootclasspath/a:../lib/boot.jar -Djb.restart.code=88 com.intellij.idea.Main carlo 24825 6368 50 16:09 pts/1 00:02:47 /usr/lib/jvm/java-6-sun/bin/java -classpath /opt/apache/apache-maven-3.0.2/boot/plexus-classworlds-2.4.jar -Dclassworlds.conf=/opt/apache/apache-maven-3.0.2/bin/m2.conf -Dmaven.home=/opt/apache/apache-maven-3.0.2 org.codehaus.plexus.classworlds.launcher.Launcher clean install carlo 25761 24825 0 16:10 pts/1 00:00:00 /bin/sh -c cd /home/carlo/work/jboss-as/testsuite/smoke && /usr/lib/jvm/java-6-sun-1.6.0.24/jre/bin/java -Dlogging.configuration=file:/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/standalone/configuration/logging.properties -Dorg.jboss.boot.log.file=/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/standalone/log/boot.log -Dorg.jboss.surefire.modular=true -Djboss.home=/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2 -jar /home/carlo/.m2/repository/org/jboss/modules/jboss-modules/1.0.0.Beta16/jboss-modules-1.0.0.Beta16.jar -mp /home/carlo/work/jboss-as/testsuite/smoke/target/modules:/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/modules -logmodule org.jboss.logmanager jboss.surefire.module /tmp/surefire4082318658493930474tmp /tmp/surefire8202241156236352551tmp carlo 25764 25761 5 16:10 pts/1 00:00:12 /usr/lib/jvm/java-6-sun-1.6.0.24/jre/bin/java -Dlogging.configuration=file:/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/standalone/configuration/logging.properties -Dorg.jboss.boot.log.file=/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/standalone/log/boot.log -Dorg.jboss.surefire.modular=true -Djboss.home=/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2 -jar /home/carlo/.m2/repository/org/jboss/modules/jboss-modules/1.0.0.Beta16/jboss-modules-1.0.0.Beta16.jar -mp /home/carlo/work/jboss-as/testsuite/smoke/target/modules:/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Beta2/modules -logmodule org.jboss.logmanager jboss.surefire.module /tmp/surefire4082318658493930474tmp /tmp/surefire8202241156236352551tmp {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated JBAS-9037: ----------------------------------- Attachment: org.jboss.as.test.embedded.demos.ejb3.StatelessBeanTestCase-output.txt Attached a thread dump in the context of the server log. This shows the hang is in the middle of deployment; i.e. there is a "Starting deployment of "ejb3-slsb-example.jar"" message but no "Completed deployment ..." No threads are blocking anywhere trying to do the deployment; the blocking threads are management layer threads waiting to be released via a notificatopn from an MSC thread that notifies a listener on the RootDeploymentUnitService. So, that callback isn't happening. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned JBAS-9037: -------------------------------------- Assignee: Stuart Douglas (was: Brian Stansberry) Stuart, I'm passing this to you as it possibly relates to the listener on the RootDeploymentUnitService where you're the expert. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Carlo de Wolf reopened JBAS-9037: --------------------------------- The bug surfaced again on https://github.com/wolfc/jboss-as/tree/JBAS-9060 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9037?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on JBAS-9037: ---------------------------------------- I ran the smoke tests 5 time with no hangs; yesterday I couldn't get a single run without a hang. I don't have Carlo's JBAS-9060 patch though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira