3 Replies Latest reply on Oct 14, 2015 5:04 AM by lafr

    Problem running standalone.sh file

    fathimasyfa
    fathimasyfa Oct 12, 2015 1:22 AM

      Hi,

        After adding all the changes to the standalone-full.xml file when i run standalone.sh i face controller Boot thread issue.It neither gives any ERROR nor moves further,It just gets pausedI even get the home page of jboss AS7 when i tried localhost:8080, but i dont find jboss running.why?

       

      sysadmin@sysadmin-OptiPlex-380:~/Desktop/jboss-as-7.1.1.Final/bin$ sudo ./standalone.sh

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

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: /home/sysadmin/Desktop/jboss-as-7.1.1.Final

       

        JAVA: java

       

        JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms1024m -Xmx1280m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

       

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

       

      10:34:18,375 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      10:34:19,356 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      10:34:19,432 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

      10:34:23,176 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      10:34:23,221 INFO  [org.xnio] XNIO Version 3.0.3.GA

      10:34:23,301 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

      10:34:23,387 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

      10:34:23,420 INFO  [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem

      10:34:23,446 INFO  [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.

      10:34:23,439 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      10:34:23,492 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

      10:34:23,474 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      10:34:23,545 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      10:34:23,545 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

      10:34:23,639 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

      10:34:24,008 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

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

      10:34:25,482 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      10:34:25,492 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

      10:34:26,422 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

      10:34:26,496 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

      10:34:26,897 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      10:34:27,020 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/deployments

      10:34:27,090 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999

      10:34:27,090 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447

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

      10:34:27,447 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 10405ms - Started 133 of 208 services (74 services are passive or on-demand)

      • 1693 Views
      • Tags:
        • 1. Re: Problem running standalone.sh file
          lafr
          lafr Oct 12, 2015 3:41 PM (in response to fathimasyfa)

          Unless you modified standalone.sh you're still using config file standalone.xml and not standalone-full.xml.

          To use standalone-full.xml instead execute ./standalone.sh --server-config=standalone-full.xml.

           

          But startup is not paused, it's ready. The last line of the output above is the final message during startup phase.

            • Actions
          • 2. Re: Problem running standalone.sh file
            fathimasyfa
            fathimasyfa Oct 14, 2015 2:34 AM (in response to fathimasyfa)

            Thanks for the response.

             

            But i am getting the same issue.will this affect the connection to the server?

             

            sysadmin@sysadmin-OptiPlex-380:~/Desktop/jboss-as-7.1.1.Final/bin$ sudo ./standalone.sh --server-config=standalone-full.xml

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

             

              JBoss Bootstrap Environment

             

              JBOSS_HOME: /home/sysadmin/Desktop/jboss-as-7.1.1.Final

             

              JAVA: java

             

              JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

             

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

             

            11:49:39,569 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

            11:49:39,708 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

            11:49:39,747 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

            11:49:40,506 INFO  [org.xnio] XNIO Version 3.0.3.GA

            11:49:40,519 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

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

            11:49:40,527 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

            11:49:40,552 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

            11:49:40,565 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 32) JBAS016200: Activating ConfigAdmin Subsystem

            11:49:40,610 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) JBAS010280: Activating Infinispan subsystem.

            11:49:40,614 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 38) JBAS016300: Activating JacORB Subsystem

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

            11:49:40,662 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

            11:49:40,716 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 48) JBAS011800: Activating Naming Subsystem

            11:49:40,719 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 49) JBAS011940: Activating OSGi Subsystem

            11:49:40,729 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

            11:49:40,735 INFO  [org.jboss.jaxr] (MSC service thread 1-3) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

            11:49:40,750 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

            11:49:40,765 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 54) JBAS013101: Activating Security Subsystem

            11:49:40,848 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

            11:49:40,889 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 58) JBAS015537: Activating WebServices Extension

            11:49:41,078 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

            11:49:41,137 INFO  [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp-localhost-127.0.0.1-8009

            11:49:41,147 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

            11:49:41,175 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started

            11:49:41,213 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/data/messagingpaging)

            11:49:41,214 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Waiting to obtain live lock

            11:49:41,286 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-1) Using AIO Journal

            11:49:41,355 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/sysadmin/Desktop/jboss-as-7.1.1.Final/standalone/deployments

            11:49:41,378 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started

            11:49:41,416 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999

            11:49:41,420 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on localhost/127.0.0.1:4447

            11:49:41,485 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

            11:49:41,510 INFO  [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-1) Waiting to obtain live lock

            11:49:41,510 INFO  [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-1) Live Server Obtained live lock

            11:49:42,100 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5455 for CORE protocol

            11:49:42,102 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5445 for CORE protocol

            11:49:42,113 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Server is now live

            11:49:42,116 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [3127b788-6ca8-11e5-af83-00232488a041]) started

            11:49:42,120 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.testQueue

            11:49:42,142 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/queue/test

            11:49:42,142 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

            11:49:42,181 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

            11:49:42,186 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.topic.testTopic

            11:49:42,239 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/topic/test

            11:49:42,243 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

            11:49:42,244 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

            11:49:42,248 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory

            11:49:42,260 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA

            11:49:42,274 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started

            11:49:42,276 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra

            11:49:42,281 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

            11:49:42,689 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

            JBAS014775:    New missing/unsatisfied dependencies:

                  service jboss.jdbc-driver.com_mysql (missing) dependents: [service jboss.data-source.java:jboss/datasources/keymanager, service jboss.data-source.java:jboss/cats/datasources/pvr]

             

            11:49:42,771 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

            11:49:42,772 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 3367ms - Started 171 of 256 services (4 services failed or missing dependencies, 78 services are passive or on-demand)

              • Actions
            • 3. Re: Problem running standalone.sh file
              lafr
              lafr Oct 14, 2015 5:04 AM (in response to fathimasyfa)

              In your original post this issue was not there, three was no issue at all.

              Now you have an issue. You have configured 2 datasources with jndi-names java:jboss/datasources/keymanager and java:jboss/cats/datasources/pvr. They are referencing a driver com.mysql which is not there.

              How did you configure your datasources? Within standalone-full.xml? Show us this section.

              Did you install the mysql driver? If yes, as a module or using the deployments folder?

                • Actions