2 Replies Latest reply: Apr 20, 2012 4:00 PM by Lin Zhao RSS

Rest deployment stuck at Waiting to obtain live lock on FileLockNodeManager

Lin Zhao Newbie

Sorry for reposting. This forum is much more active than the developer forum.

 

I have a hornetq standalone 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.

 

I use JBoss Web/7.0.13.Final and HornetQ Server version 2.2.5.GA

 

Trace:

 

 

10:21:59,713 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

10:21:59,875 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

10:21:59,919 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

10:22:00,582 INFO  [org.xnio] XNIO Version 3.0.3.GA

10:22:00,582 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

10:22:00,593 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

10:22:00,602 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

10:22:00,615 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

10:22:00,618 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

10:22:00,625 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

10:22:00,625 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

10:22:00,627 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

10:22:00,631 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

10:22:00,636 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

10:22:00,643 INFO  [org.jboss.as.security] (MSC service thread 1-14) JBAS013100: Current PicketBox version=4.0.7.Final

10:22:00,678 INFO  [org.jboss.as.connector] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

10:22:00,688 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

10:22:00,713 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-12) JBAS015400: Bound mail session [java:jboss/mail/Default]

10:22:00,734 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-9) JBoss Web Services - Stack CXF Server 4.0.2.GA

10:22:00,749 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

10:22:00,839 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-9) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

10:22:01,068 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

10:22:01,304 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "jboss-as-helloworld.war"

10:22:01,318 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-10) JBAS015012: Started FileSystemDeploymentService for directory /Users/lin/Downloads/jboss-as-7.1.1.Final/standalone/deployments

10:22:01,320 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment rest.war

10:22:01,325 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

10:22:01,326 INFO  [org.jboss.as.remoting] (MSC service thread 1-16) JBAS017100: Listening on /127.0.0.1:9999

10:22:01,326 INFO  [org.jboss.as.remoting] (MSC service thread 1-14) JBAS017100: Listening on localhost/127.0.0.1:4447

10:22:01,568 INFO  [org.jboss.weld.deployer] (MSC service thread 1-13) JBAS016002: Processing weld deployment jboss-as-helloworld.war

10:22:01,616 INFO  [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016005: Starting Services for CDI deployment: jboss-as-helloworld.war

10:22:01,637 INFO  [org.jboss.weld.Version] (MSC service thread 1-12) WELD-000900 1.1.5 (AS71)

10:22:01,659 INFO  [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016008: Starting weld service for deployment jboss-as-helloworld.war

10:22:01,964 INFO  [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld

10:22:01,976 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "jboss-as-helloworld.war"

10:22:01,981 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

10:22:01,982 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "rest.war"

10:22:01,982 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2553ms - Started 190 of 269 services (76 services are passive or on-demand)

10:22:02,726 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-11) 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.2.4.jar"  does not point to a valid jar for a Class-Path reference.

10:22:02,727 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-11) 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.2.4.jar"  does not point to a valid jar for a Class-Path reference.

10:22:02,728 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-11) 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.2.4.jar"  does not point to a valid jar for a Class-Path reference.

10:22:02,729 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-11) 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.2.4.jar"  does not point to a valid jar for a Class-Path reference.

10:22:02,747 INFO  [org.jboss.as.pojo] (MSC service thread 1-10) JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).

10:22:03,074 WARNING [org.hornetq.core.deployers.impl.FileConfigurationParser] (MSC service thread 1-8) 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

10:22:03,103 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) 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)

10:22:03,105 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) Waiting to obtain live lock

10:22:03,125 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-8) Using NIO Journal

10:22:03,141 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) 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.

10:22:08,302 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-8) Waiting to obtain live lock

10:23:01,331 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "rest.war" was rolled back with failure message Operation cancelled

10:23:01,331 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.