3 Replies Latest reply on Dec 12, 2013 4:14 AM by Wolf-Dieter Fink

    Unable to start the jboss-6.1.0.Final in RHEL 5.4

    Narendra Reddy Newbie

      Hi,

       

      when i am trying to install jboss-6.1.0.Final in RHEL 5.4 OS, getting below error message. so kindly help me to sort out ASAP.

       

      [root@mailserverbkp bin]# cat /etc/issue

      Red Hat Enterprise Linux Server release 5.4 (Tikanga)

      Kernel \r on an \m

      [root@mailserverbkp bin]# pwd

      /opt/product/jboss-eap-6.1/bin

      [root@mailserverbkp bin]# ./standalone.sh

       

      ./standalone.sh: line 78: cd: /opt/product/jboss-6.1.0.Final: No such file or directory

       

         WARNING:  JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.

       

       

                   JBOSS_HOME: /opt/product/jboss-6.1.0.Final

       

       

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

       

       

        JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /opt/product/jboss-6.1.0.Final

       

       

        JAVA: /usr/java/jdk1.7.0_40/bin/java

       

       

        JAVA_OPTS:  -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

       

       

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

       

       

      Error: Unable to access jarfile /opt/product/jboss-6.1.0.Final/jboss-modules.jar

       

       

      Please let me know why it is throughing above mentioned error. Is there any prerequisites required to install jboss. 

        • 1. Re: Unable to start the jboss-6.1.0.Final in RHEL 5.4
          jaikiran pai Master
          so kindly help me to sort out ASAP.

          Calm down Everyone here is a volunteer and words like "urgent" and "ASAP" tend to drive volunteers away from that thread.

           

          As for the issue you are running into? Are you setting JBOSS_HOME? Do  not do that. The startup script will do it for you automatically. All you have to do is unzip the binary, set JAVA_HOME (the location where JDK/JRE is installed) and run the server startup script.

          • 2. Re: Unable to start the jboss-6.1.0.Final in RHEL 5.4
            Narendra Reddy Newbie

            Hi Jai..

             

            JAVA_HOME has been set and JBOSS_HOME also as well.. but the thing is here i am not able to install jboss. it throws below error..and stopping there so i terminated the installatation..

             

            [root@mailserverbkp bin]# ./standalone.sh

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

             

             

              JBoss Bootstrap Environment

             

             

              JBOSS_HOME: /opt/product/jboss-eap-6.1

             

             

              JAVA: /usr/java/jdk1.7.0_40/bin/java

             

             

              JAVA_OPTS:  -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

             

             

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

             

             

            12:51:20,236 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1

            12:51:20,435 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1

            12:51:20,506 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting

            12:51:21,661 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1

            12:51:21,667 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

            12:51:21,669 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

            12:51:21,676 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.16.GA-redhat-1

            12:51:21,792 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

            12:51:21,839 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem

            12:51:21,861 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

            12:51:21,970 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.

            12:51:21,993 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

            12:51:22,003 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem

            12:51:22,175 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension

            12:51:22,204 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1

            12:51:22,240 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

            12:51:22,270 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)

            12:51:22,504 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3

            12:51:22,642 WARN  [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.

            12:51:22,757 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

            12:51:22,790 ERROR [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003043: Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080

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

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

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

                    at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:273) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

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

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

                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]

                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]

                    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]

             

             

            12:51:22,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector

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

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

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

                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]

                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]

                    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]

            Caused by: LifecycleException:  JBWEB000023: Protocol handler initialization failed

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

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

                    ... 5 more

             

             

            12:51:22,952 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999

            12:51:22,953 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447

            12:51:22,956 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/product/jboss-eap-6.1/standalone/deployments

            12:51:23,043 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

            JBAS014777:   Services which failed to start:      service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector

             

             

            12:51:23,055 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

            12:51:23,056 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

            12:51:23,056 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started (with errors) in 3209ms - Started 122 of 177 services (1 services failed or missing dependencies, 53 services are passive or on-demand)

            *** JBossAS process (32237) received INT signal ***

            12:51:31,278 INFO  [org.apache.catalina.core] (MSC service thread 1-3) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started

            12:51:31,283 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]

            12:51:31,326 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) stopped in 2ms

            *** JBossAS process (32237) received TERM signal ***

            • 3. Re: Unable to start the jboss-6.1.0.Final in RHEL 5.4
              Wolf-Dieter Fink Master

              There is a message that localhost can not be resolved, you might have a network configuration problem.

              Also there is a different process which use port 8080, but this might be a wrong message related to the first warning.

               

              12:51:22,642 WARN  [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.

              12:51:22,790 ERROR [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003043: Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080