Rest deployment stuck at Waiting to obtain live lock on FileLockNodeManager
Hi I have a hornetq instance running on localhost and followed http://docs.jboss.org/resteasy/hornetq-rest/1.0-beta-1/userguide/html_single/index.html#d0e69 to set up a jboss Rest server also on localhost. When deploying the .war it gets stuck at
09:58:28,187 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Waiting to obtain live lock
for like 60 seconds then rolled back. Any advice what may have caused this? The hornetq instance works well as a standalone through Stomp.
Full trace:
09:58:19,613 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
09:58:19,775 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
09:58:19,820 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
09:58:20,429 INFO [org.xnio] XNIO Version 3.0.3.GA
09:58:20,429 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
09:58:20,438 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
09:58:20,446 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
09:58:20,461 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
09:58:20,465 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
09:58:20,472 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
09:58:20,474 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
09:58:20,476 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
09:58:20,481 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
09:58:20,488 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final
09:58:20,495 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
09:58:20,524 INFO [org.jboss.as.connector] (MSC service thread 1-9) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
09:58:20,537 INFO [org.jboss.as.naming] (MSC service thread 1-16) JBAS011802: Starting Naming Service
09:58:20,550 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
09:58:20,600 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-15) JBoss Web Services - Stack CXF Server 4.0.2.GA
09:58:20,609 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
09:58:20,679 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
09:58:20,895 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
09:58:21,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "jboss-as-helloworld.war"
09:58:21,154 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments
09:58:21,156 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment rest.war
09:58:21,160 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found rest.war in deployment directory. To trigger deployment create a file called rest.war.dodeploy
09:58:21,164 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447
09:58:21,164 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /127.0.0.1:9999
09:58:21,418 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment jboss-as-helloworld.war
09:58:21,469 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-as-helloworld.war
09:58:21,490 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
09:58:21,513 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment jboss-as-helloworld.war
09:58:21,818 INFO [org.jboss.web] (MSC service thread 1-10) JBAS018210: Registering web context: /jboss-as-helloworld
09:58:21,830 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "jboss-as-helloworld.war"
09:58:21,835 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
09:58:21,836 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "rest.war"
09:58:21,836 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2487ms - Started 190 of 269 services (76 services are passive or on-demand)
09:58:22,561 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jaxb-api.jar in "/Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments/rest.war/WEB-INF/lib/jaxb-impl-2.1.12.jar" does not point to a valid jar for a Class-Path reference.
09:58:22,561 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry activation.jar in "/Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments/rest.war/WEB-INF/lib/jaxb-impl-2.1.12.jar" does not point to a valid jar for a Class-Path reference.
09:58:22,562 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jsr173_1.0_api.jar in "/Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments/rest.war/WEB-INF/lib/jaxb-impl-2.1.12.jar" does not point to a valid jar for a Class-Path reference.
09:58:22,563 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jaxb1-impl.jar in "/Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments/rest.war/WEB-INF/lib/jaxb-impl-2.1.12.jar" does not point to a valid jar for a Class-Path reference.
09:58:22,681 INFO [org.jboss.as.pojo] (MSC service thread 1-1) JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
09:58:22,997 WARNING [org.hornetq.core.deployers.impl.FileConfigurationParser] (MSC service thread 1-1) AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
09:58:23,026 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/var/groupon/hornetq/journal,bindingsDirectory=/var/groupon/hornetq/bindings,largeMessagesDirectory=/var/groupon/hornetq/large-messages,pagingDirectory=/var/groupon/hornetq/paging)
09:58:23,027 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Waiting to obtain live lock
09:58:23,053 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-1) Using NIO Journal
09:58:23,062 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) 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.
09:58:28,187 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Waiting to obtain live lock
09:59:21,164 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "rest.war" was rolled back with failure message Operation cancelled
09:59:21,165 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.