1 Reply Latest reply on Jul 13, 2013 3:59 AM by Sri Ram

    JBoss 7.1.1 Deployment Failure on Bizagi BPM Suite

    Morty S Newbie

      Good day

       

      I'd appreciate any help or leads to solve this problem.

      I am trying to publish a process using Bizagi (a BPM Suite), which comes bundled with JBoss 7.1.1. Under the deployment folder there is a BizAgi-ear-JBoss.ear file that I suppose should be deployed. When I publish the process from within Bizagi, the .ear file is also deployed, but ends up as BizAgi-ear-JBoss.ear.failed , and displays the following message:

       

       

      And the log from the Server is:

       

       

      10:42:43,663 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
      10:42:44,443 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
      10:42:44,646 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
      10:42:44,880 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
      10:42:46,580 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
      10:42:46,627 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
      10:42:48,203 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
      10:42:48,827 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
      10:42:50,075 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
      10:42:51,136 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
      10:42:51,151 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
      10:42:51,167 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
      10:42:51,198 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
      10:42:51,198 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [cdb8d2aa-e9aa-11e2-90a4-001d92219e28]) started
      10:42:51,229 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
      10:42:51,715 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
      10:42:51,840 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
      10:42:52,027 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
      10:42:52,043 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      10:42:52,043 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
      10:42:52,059 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.topic.testTopic
      10:42:52,199 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
      10:42:52,230 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.AsyncController
      10:42:52,230 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
      10:42:52,339 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/BizAgiJava]
      10:42:52,339 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
      10:42:52,371 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-2) HornetQ resource adaptor started
      10:42:52,371 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
      10:42:52,386 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      10:42:52,885 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
      10:42:52,917 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0.0.0.0:9999
      10:42:52,901 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment BizAgi-ear-JBoss.ear
      10:42:52,917 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
      10:42:53,815 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
      10:43:52,971 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.
      10:43:52,971 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
      10:44:09,289 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
      10:44:09,289 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
      10:44:09,305 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-war.war"
      10:44:09,305 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry Generated.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar"  does not point to a valid jar for a Class-Path reference.
      10:44:12,627 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3323ms
      10:44:12,659 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry Generated.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,659 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,659 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,659 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,674 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,674 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,674 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,690 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,690 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,690 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,690 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,705 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,705 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,705 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,705 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,705 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,721 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,721 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,721 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,721 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,721 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,752 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,752 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,752 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,752 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,768 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,768 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,768 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:44:12,815 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 3516ms
      10:44:19,023 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-war.war in 9727ms
      10:44:19,195 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 26220ms
      10:48:07,190 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/queue/test
      10:48:07,208 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
      10:48:07,211 INFO  [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011942: Stopping OSGi Framework
      10:48:07,215 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
      10:48:07,218 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
      10:48:26,386 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
      10:48:26,574 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
      10:48:26,835 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
      10:48:27,355 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
      10:48:27,368 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
      10:48:27,834 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-0.0.0.0-0.0.0.0-8080
      10:48:28,030 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
      10:48:28,051 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
      10:48:28,505 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
      10:48:28,684 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
      10:48:28,699 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:9999
      10:48:28,892 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/BizAgiJava]
      10:48:28,963 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
      10:48:29,208 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
      10:48:29,217 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
      10:48:29,226 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
      10:48:29,232 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) Server is now live
      10:48:29,235 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [a8525f7d-ea06-11e2-8bd6-001d92219e28]) started
      10:48:29,244 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.testQueue
      10:48:29,383 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/queue/test
      10:48:29,415 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
      10:48:29,419 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.topic.testTopic
      10:48:29,478 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/topic/test
      10:48:29,483 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      10:48:29,488 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
      10:48:29,491 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.AsyncController
      10:48:29,499 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
      10:48:29,593 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
      10:48:29,626 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
      10:48:29,629 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
      10:48:29,635 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      10:48:29,915 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
      10:48:29,919 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 10236ms - Started 157 of 234 services (76 services are passive or on-demand)
      10:48:33,608 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments\BizAgi-ear-JBoss.ear. Deployment changes will not be processed until all content is complete.
      10:48:35,220 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
      10:49:35,047 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.
      10:49:35,048 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
      10:49:39,124 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
      10:49:39,127 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
      10:49:39,128 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "BizAgi-war.war"
      10:49:39,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 21ms
      10:49:42,348 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3219ms
      10:49:44,384 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,392 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,399 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,404 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,409 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,414 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,419 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,424 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,429 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,435 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,440 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,445 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,450 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,455 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,461 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,466 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,470 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,475 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,480 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,485 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,491 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,496 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,501 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,506 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,511 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,516 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,521 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,526 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,531 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,537 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,542 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:44,547 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:49:55,978 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/queue/test
      10:49:56,073 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
      10:49:56,083 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
      10:49:56,087 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
      10:50:11,751 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
      10:50:11,889 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
      10:50:12,481 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
      10:50:12,766 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
      10:50:13,228 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
      10:50:13,248 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
      10:50:13,626 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
      10:50:13,792 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
      10:50:14,783 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/BizAgiJava]
      10:50:14,877 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
      10:50:14,930 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
      10:50:14,930 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:9999
      10:50:14,990 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
      10:50:15,330 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
      10:50:15,336 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
      10:50:15,346 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
      10:50:15,353 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
      10:50:15,360 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [e786cb0a-ea06-11e2-8e59-001d92219e28]) started
      10:50:15,373 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.queue.AsyncController
      10:50:15,502 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
      10:50:15,539 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
      10:50:15,544 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
      10:50:15,548 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.queue.testQueue
      10:50:15,566 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/queue/test
      10:50:15,572 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      10:50:15,585 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.topic.testTopic
      10:50:15,712 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA
      10:50:15,757 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/topic/test
      10:50:15,769 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-3) HornetQ resource adaptor started
      10:50:15,781 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra
      10:50:15,788 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      10:50:16,094 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
      10:50:16,097 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 11046ms - Started 157 of 234 services (76 services are passive or on-demand)
      10:50:20,528 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
      10:51:13,401 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-war.war"
      10:51:13,404 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
      10:51:13,409 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
      10:51:17,466 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,471 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,476 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,481 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,486 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,491 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,496 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,506 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,511 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,516 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,521 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,526 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,532 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,537 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,544 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,549 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,554 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,559 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,564 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,569 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,574 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,579 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,584 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,589 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,594 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,599 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,604 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,609 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,614 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,619 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:17,624 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:51:18,557 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,563 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,570 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,576 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,582 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,593 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,599 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,611 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,635 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,680 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,685 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,690 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,695 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,700 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
      10:51:18,707 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,732 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,740 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,741 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,741 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,741 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,756 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,756 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,756 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,772 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter'
      10:51:18,803 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,850 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,850 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,850 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
      10:51:18,819 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
      10:51:18,912 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
      10:51:18,975 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for BizAgi.RenderPU
      10:51:18,975 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for BizAgi.EntitiesPU
      10:51:20,503 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
      10:51:20,503 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.
      10:51:20,909 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 156ms
      10:51:20,909 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 160ms
      10:51:32,609 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-war.war in 11864ms
      10:51:32,937 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 12192ms
      10:51:34,200 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
      10:51:34,200 INFO  [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011942: Stopping OSGi Framework
      10:51:34,200 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
      10:51:34,216 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,216 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,216 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,216 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,231 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,231 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,231 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,231 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,247 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,247 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,247 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,247 WARN  [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
      10:51:34,263 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011605: Unbound messaging object to jndi name java:/jms/AsyncController
      10:51:34,278 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/topic/test
      10:51:34,294 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/queue/test
      10:51:34,309 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
      10:51:48,583 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
      10:51:48,537 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
      10:51:49,223 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
      10:51:50,253 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
      10:51:50,721 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
      10:51:50,736 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
      10:51:50,752 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
      10:51:51,516 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-0.0.0.0-8080
      10:51:51,672 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
      10:51:52,281 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
      10:51:52,327 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
      10:51:52,327 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
      10:51:52,327 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
      10:51:52,343 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [21248c49-ea07-11e2-916d-001d92219e28]) started
      10:51:52,374 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/BizAgiJava]
      10:51:52,437 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      10:51:52,483 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
      10:51:52,499 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.queue.AsyncController
      10:51:52,686 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
      10:51:52,686 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
      10:51:52,717 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
      10:51:52,733 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
      10:51:52,764 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.topic.testTopic
      10:51:52,780 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
      10:51:52,827 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/topic/test
      10:51:52,858 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
      10:51:52,920 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /0.0.0.0:9999
      10:51:52,920 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
      10:51:52,920 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
      10:51:52,920 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
      10:51:52,936 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      10:51:53,263 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
      10:51:53,263 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 10857ms - Started 157 of 234 services (76 services are passive or on-demand)
      10:51:57,850 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
      10:52:57,827 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.
      10:52:57,852 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
      10:53:12,248 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-war.war"
      10:53:12,252 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
      10:53:12,253 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
      10:53:15,931 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3670ms
      10:53:15,940 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 3681ms
      10:53:16,667 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,672 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,683 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,689 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,695 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,701 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,710 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,715 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,720 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,726 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,731 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,736 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,741 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,747 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,752 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,757 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,767 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,772 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,777 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,783 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,788 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,793 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,798 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,803 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,808 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,813 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,818 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,823 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,828 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:16,833 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war"  does not point to a valid jar for a Class-Path reference.
      10:53:22,629 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-war.war in 10370ms
      10:53:22,787 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 24927ms
      

       

      Can someone please guide me on what possible problems could be, I am not an expert in JBoss...

       

      Further information:

       

      I am running the latest Java version 7, update 25, on a Windows 7 Enterprise machine.

       

      Thanks in advance

        • 1. Re: JBoss 7.1.1 Deployment Failure on Bizagi BPM Suite
          Sri Ram Newbie

          From the log file,

          10:43:52,971 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.

          10:43:52,971 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled

           

          10:48:33,608 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments\BizAgi-ear-JBoss.ear. Deployment changes will not be processed until all content is complete.

           

          It seems that the deployment of 'BizAgi-ear-JBoss.ear takes more time (>60 secs) to deploy, its failed with timeout error.

           

          I think deployment takes more time, because it tries to connect to jmx port (:9999) & failed

          2013-07-11 10:48:13,121 [main] ERROR com.bizagi.console.appserver.MBeanManagerJBoss  -

          java.lang.RuntimeException: Operation failed with status WAITING

                  at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:154)

                  at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:95)

                  at com.bizagi.console.appserver.MBeanManagerJBoss.isServerStarted(MBeanManagerJBoss.java:43)

                  at com.bizagi.console.model.AbstractAppServerManagerDelegate.executeStopAppServer(AbstractAppServerManagerDelegate.java:350)

                  at com.bizagi.console.model.JbossManagerDelegate.refreshAppServer(JbossManagerDelegate.java:60)

                  at com.bizagi.console.controller.AppServerManagerController.refreshAppServer(AppServerManagerController.java:198)

                  at com.bizagi.console.view.cmdline.app.CommandLineView.processRequest(CommandLineView.java:49)

                  at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:57)

           

          Deployment directory seems to be "C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments". But why those class-path entries points to this "C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/" directories? Can you explain your deployment structure?

           

          Did you properly configured the JBoss (especially authentication part)?