JBoss AS 7.1CR1 hangs when deployments reference JMS objects
I was going to report this as a bug, but I read http://community.jboss.org/wiki/HelpBugReport first!
If you build and deploy the attached application (required Maven 3.0.x), start the server with standalone-full.xml profile, and then try to terminate it with Ctrl-C, the server will hang:
18:51:32,049 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.0.GA
18:51:32,174 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/steve/servers/jboss-as-7.1.0.CR1/standalone/data/messagingjournal,bindingsDirectory=/Users/steve/servers/jboss-as-7.1.0.CR1/standalone/data/messagingbindings,largeMessagesDirectory=/Users/steve/servers/jboss-as-7.1.0.CR1/standalone/data/messaginglargemessages,pagingDirectory=/Users/steve/servers/jboss-as-7.1.0.CR1/standalone/data/messagingpaging)
18:51:32,343 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
18:51:32,366 INFO [org.apache.tomcat.util.net.AprEndpoint] (MSC service thread 1-4) Failed to create poller with specified size of 32768
18:51:32,367 WARN [jacorb.codeset] (MSC service thread 1-5) Warning - unknown codeset (MacRoman) - defaulting to ISO-8859-1
18:51:32,380 INFO [org.apache.tomcat.util.net.AprEndpoint] (MSC service thread 1-4) Failed to create poller with specified size of 32768
18:51:32,386 INFO [org.apache.tomcat.util.net.AprEndpoint] (MSC service thread 1-4) Failed to create poller with specified size of 16384
18:51:32,389 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
18:51:32,391 INFO [org.jboss.as.jacorb] (MSC service thread 1-5) CORBA ORB Service Started
18:51:32,569 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) CORBA Naming Service Started
18:51:32,714 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:5455 for CORE protocol
18:51:32,716 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:5445 for CORE protocol
18:51:32,727 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Server is now live
18:51:32,728 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [b50df0ad-3097-11e1-a495-9027e4faed49] started
18:51:32,804 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
18:51:32,808 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
18:51:32,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:51:32,862 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /127.0.0.1:9999
18:51:32,901 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /Users/steve/servers/jboss-as-7.1.0.CR1/standalone/deployments
18:51:32,920 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
18:51:32,946 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-6) HornetQ resource adaptor started
18:51:32,946 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
18:51:32,948 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
18:51:32,961 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
18:51:32,963 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
18:51:32,964 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) trying to deploy queue jms.topic.testTopic
18:51:32,995 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/topic/test
18:51:33,066 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "messaging-app-1.0-SNAPSHOT.ear"
18:51:33,446 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "messaging-web-1.0-SNAPSHOT.war"
18:51:33,446 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "messaging-ejb-1.0-SNAPSHOT.jar"
18:51:33,909 INFO [org.jboss.weld] (MSC service thread 1-7) Processing CDI deployment: messaging-app-1.0-SNAPSHOT.ear
18:51:33,995 INFO [org.jboss.weld] (MSC service thread 1-3) Processing CDI deployment: messaging-ejb-1.0-SNAPSHOT.jar
18:51:33,998 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named Messenger in deployment unit subdeployment "messaging-ejb-1.0-SNAPSHOT.jar" of deployment "messaging-app-1.0-SNAPSHOT.ear" are as follows:
java:global/messaging-app-1.0-SNAPSHOT/messaging-ejb-1.0-SNAPSHOT/Messenger!org.jboss.as7.demo.ejb.Messenger
java:app/messaging-ejb-1.0-SNAPSHOT/Messenger!org.jboss.as7.demo.ejb.Messenger
java:module/Messenger!org.jboss.as7.demo.ejb.Messenger
java:global/messaging-app-1.0-SNAPSHOT/messaging-ejb-1.0-SNAPSHOT/Messenger
java:app/messaging-ejb-1.0-SNAPSHOT/Messenger
java:module/Messenger
18:51:34,020 INFO [org.jboss.weld] (MSC service thread 1-4) Processing CDI deployment: messaging-web-1.0-SNAPSHOT.war
18:51:34,038 INFO [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: messaging-app-1.0-SNAPSHOT.ear
18:51:34,071 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.4 (Final)
18:51:34,097 INFO [org.jboss.weld] (MSC service thread 1-2) Starting weld service
18:51:34,430 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Solder Config XML provider starting...
18:51:34,431 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider
18:51:34,438 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Reading XML file: vfs:/content/messaging-app-1.0-SNAPSHOT.ear/messaging-ejb-1.0-SNAPSHOT.jar/META-INF/beans.xml
18:51:34,444 INFO [org.jboss.solder.Version] (MSC service thread 1-2) Solder null (build id: null)
18:51:36,120 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/messaging-demo'
18:51:36,924 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-4) Hibernate Validator 4.2.0.Final
18:51:37,091 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /messaging-demo
18:51:37,092 INFO [org.jboss.as] (MSC service thread 1-7) JBoss AS 7.1.0.CR1 "Flux Capacitor" started in 6963ms - Started 297 of 373 services (74 services are passive or on-demand)
18:51:37,166 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "messaging-app-1.0-SNAPSHOT.ear"
^C18:51:43,518 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
18:51:43,519 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011921: Stopping OSGi Framework
18:51:43,521 INFO [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
18:51:43,554 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
18:51:43,560 INFO [jacorb.poa] POA IRPOA destroyed
18:51:43,570 INFO [jacorb.poa] POA Naming destroyed
18:51:43,576 INFO [org.apache.coyote.http11.Http11AprProtocol] Pausing Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
18:51:43,577 INFO [org.apache.coyote.http11.Http11AprProtocol] Stopping Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
18:51:43,579 ERROR [org.hornetq.core.server.impl.ServerSessionImpl] Cannot find consumer with id 0
18:51:43,584 INFO [jacorb.poa] POA RootPOA destroyed
18:51:43,586 INFO [jacorb.orb] prepare ORB for shutdown...
18:51:43,586 INFO [jacorb.orb] ORB going down...
18:51:43,600 INFO [jacorb.orb] ORB shutdown complete
18:51:43,601 INFO [jacorb.orb] ORB run, exit
18:51:43,600 INFO [jacorb.orb.iiop] Listener exited
18:51:43,606 ERROR [org.hornetq.core.server.impl.ServerSessionImpl] Cannot find consumer with id 0
18:51:43,604 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,616 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,616 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,631 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,637 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,638 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,643 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,646 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,649 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,649 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,652 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,656 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,658 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,658 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,660 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4]
18:51:43,706 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [b50df0ad-3097-11e1-a495-9027e4faed49] stopped
