1 Reply Latest reply on May 25, 2015 9:46 AM by jaysensharma

    Hi I am new in jboss trying to configure manually but getting same error n times.even i try to stop process but no use kindly help

    gauri.patil

      @

      @ !run_server.sh

       

      D:\jbpm\jbpm\jboss-eap-6.0\bin>cd D:\jbpm\jbpm\jboss-eap-6.0\bin

       

      D:\jbpm\jbpm\jboss-eap-6.0\bin>set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_33

       

      D:\jbpm\jbpm\jboss-eap-6.0\bin>echo

      ECHO is on.

       

      D:\jbpm\jbpm\jboss-eap-6.0\bin>standalone.bat -Dorg.jboss.aslogging.per_deployment=false -b 127.0.0.1

      Calling "D:\jbpm\jbpm\jboss-eap-6.0\bin\standalone.conf.bat"

      ===============================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: D:\jbpm\jbpm\jboss-eap-6.0

       

        JAVA: C:\Program Files\Java\jdk1.6.0_33\bin\java

       

        JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms256M -Xmx256M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4St

      ss.socket.binding.port-offset=1000

       

      ===============================================================================

       

      16:11:15,543 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1

      16:11:15,668 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2

      16:11:15,715 INFO  [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

      16:11:16,479 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found jbpm-human-task.war in deployment directory. To trigger deployment create a file called jbpm-human-task.war.dodeplo

      16:11:16,479 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found jboss-brms.war in deployment directory. To trigger deployment create a file called jboss-brms.war.dodeploy

      16:11:16,479 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found business-central.war in deployment directory. To trigger deployment create a file called business-central.war.dodep

      16:11:16,479 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found business-central-server.war in deployment directory. To trigger deployment create a file called business-central-se

      16:11:16,479 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found designer.war in deployment directory. To trigger deployment create a file called designer.war.dodeploy

      16:11:16,479 INFO  [org.xnio] XNIO Version 3.0.7.GA-redhat-1

      16:11:16,495 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      16:11:16,495 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1

      16:11:16,495 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1

      16:11:16,510 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      16:11:16,573 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

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

      16:11:16,588 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)

      16:11:16,604 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      16:11:16,775 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      16:11:16,775 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem

      16:11:16,822 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

      16:11:16,838 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem

      16:11:16,853 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

      16:11:16,869 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2

      16:11:17,087 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Error initializing endpoint: java.net.BindException: Address already in use: JVM_Bind /127.0.0.1:9089

              at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:984) [jbossweb-7.0.17.Final-redhat-1.jar:]

              at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.17.Final-redhat-1.jar:]

              at org.apache.catalina.connector.Connector.init(Connector.java:1001) [jbossweb-7.0.17.Final-redhat-1.jar:]

              at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:268) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

       

      16:11:17,119 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.c

              at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:272)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

      Caused by: LifecycleException:  Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind /127.0.0.1:9089

              at org.apache.catalina.connector.Connector.init(Connector.java:1003)

              at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:268)

              ... 5 more

       

      16:11:17,228 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2

      16:11:17,399 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory D:\jbpm\jbpm\jboss-eap-6.0\standalone\deployme

      16:11:17,415 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jbo

              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:110)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

      Caused by: java.net.BindException: Address already in use: bind

              at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_33]

              at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)

              at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)

              at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:258)

              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:102)

              ... 5 more

       

      16:11:17,665 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]

      16:11:17,540 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in ser

              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:110)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

      Caused by: java.net.BindException: Address already in use: bind

              at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_33]

              at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)

              at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)

              at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:258)

              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:102)

              ... 5 more

       

      16:11:17,555 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartExcepti

              at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:218) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

      Caused by: java.net.BindException: Address already in use: bind

              at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_33]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_33]

              at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)

              at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)

              at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)

              at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)

              at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:150)

              at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:184) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

              ... 5 more

       

      16:11:18,351 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Addres

            service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector

            service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Address already in use: bind 127.0.

            service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind

       

      16:11:18,507 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015964: Http management interface is not enabled

      16:11:18,507 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled

      16:11:18,507 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started (with errors) in 3151ms - Started 129 of 217 services (7 services fails)

       

      standalon.bat

       

       

      Calling "D:\jbpm\jbpm\jboss-eap-6.0\bin\standalone.conf.bat"

      ===============================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: D:\jbpm\jbpm\jboss-eap-6.0

       

        JAVA: C:\Program Files\Java\jdk1.6.0_33\bin\java

       

        JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms256M -Xmx256M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.wa

      ss.socket.binding.port-offset=1000

       

      ===============================================================================

       

      16:11:06,823 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1

      16:11:06,963 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2

      16:11:07,025 INFO  [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

      16:11:07,805 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found jbpm-human-task.war in deployment directory. To trigger deployment create a file called jbpm-human-task.war.dodeploy

      16:11:07,805 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found jboss-brms.war in deployment directory. To trigger deployment create a file called jboss-brms.war.dodeploy

      16:11:07,805 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found business-central.war in deployment directory. To trigger deployment create a file called business-central.war.dodeploy

      16:11:07,805 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found business-central-server.war in deployment directory. To trigger deployment create a file called business-central-server.war.dodeploy

      16:11:07,805 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found designer.war in deployment directory. To trigger deployment create a file called designer.war.dodeploy

      16:11:07,805 INFO  [org.xnio] XNIO Version 3.0.7.GA-redhat-1

      16:11:07,821 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      16:11:07,821 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1

      16:11:07,821 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1

      16:11:07,837 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      16:11:07,852 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      16:11:07,852 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      16:11:07,883 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      16:11:07,883 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem

      16:11:07,915 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem

      16:11:07,930 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)

      16:11:07,946 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      16:11:07,977 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      16:11:08,273 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

      16:11:08,305 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2

      16:11:08,476 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2

      16:11:08,476 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

      16:11:08,648 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory D:\jbpm\jbpm\jboss-eap-6.0\standalone\deployments

      16:11:08,679 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:10988

      16:11:08,679 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:5447

      16:11:08,695 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-/127.0.0.1:9089

      16:11:08,960 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]

      16:11:09,038 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:10990/management

      16:11:09,053 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:10990

      16:11:09,053 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 2449ms - Started 136 of 217 services (80 services are passive or on-demand)