4 Replies Latest reply on May 8, 2013 10:44 PM by mazz

    RHQ 4.7 trying to bind to 8080?

    Newbie

      I've upgraded my 4.6 to 4.7 and upon starting, i'm getting errors with jbossweb trying to start on 8080.

      I have other services and apps running on this server and one does use 8080. RHQ typically has bound to 7080 and I've had no conflicts. Is this just default standalone.xml cruft left in the jbossAS config? What's the best advice on ripping it out so I get a clean start?

       

       

       

      19:05:52,384 ERROR [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003043: Error initializing endpoint: java.net.BindException: Address already in use /0.0.0.0:8080

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

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

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

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

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

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

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24]

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

              at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]

       

      19:05:52,427 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: 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.jar:1.0.4.GA]

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

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24]

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

              at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]

      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

        • 1. Re: RHQ 4.7 trying to bind to 8080?
          Newbie

          realized i had to re-run the rhq-installer.sh.

          • 2. Re: RHQ 4.7 trying to bind to 8080?
            mazz Master

            First, the recommendation is to run the RHQ Server on its own box.

             

            But things can work if you want to run other things on the box. However, you'll have to keep in mind conflicts like this can happen.

             

            When you unzip RHQ Server and run it, what you are running is a out-of-box, stock JBossAS (for RHQ 4.7, its a stock EAP 6.1.alpha release). This means you are running an app server that will listen to the default port 8080. It is only when you finish the installation by running rhq-installer.sh will the ports be re-assigned to the ports specified in rhq-server.properties. (this behavior is different than RHQ 4.5 and earlier when the old GUI installer was used).

             

            But you aren't even getting far enough to run the installer because you have something running on 8080.

             

            You can get around this by shutting down what you have listening on 8080, run the RHQ Server, run the RHQ installer, and then you can restart whatever it is you had listening on 8080. After RHQ has been fully installed, it will be listening to 7080 and port 8080 will no longer be used.

             

            If you don't want to shutdown your server listening on 8080, you'll have to do a minor manual edit to RHQ Server's underlying EAP instance. Edit <rhq-server-install>/jbossas/standalone/configuration/standalone-full.xml and change <socket-binding name="http" port="8080" /> you find at the bottom of that file so it is 7080. Assuming no other ports are in conflict, you can start the RHQ Server and then finish the installation via the rhq-installer.sh script.

            1 of 1 people found this helpful
            • 3. Re: RHQ 4.7 trying to bind to 8080?
              Newbie

              Thanks mazz. That is what I was circling around. The installer actually ran even with the http port conflict and then rhq started without conflict after.

               

              Now I'm getting the default EAP 6 welcome page instead of the app.

               

              Only thing in the installer logs was the below...

              Seemed odd as it says it created the keystore then says it can't find it. I'll keep digging.

               

              20:41:18,536 INFO  [org.rhq.enterprise.server.installer.ServerInstallUtil] New keystore created [/opt/rhq-server/jbossas/standalone/configuration/rh

              q.keystore] with cert domain name of [CN=rhqserver.hnw.com, OU=RHQ, O=rhq-project.org, C=US]

              20:41:18,550 INFO  [org.rhq.enterprise.server.installer.ServerInstallUtil] Creating https connector...

              20:41:18,560 WARN  [org.rhq.enterprise.server.installer.ServerInstallUtil] Missing both keystore [rhq.keystore] and truststore [rhq.truststore]

              20:41:18,849 ERROR [org.rhq.enterprise.server.installer.Installer] An error occurred: org.rhq.common.jbossas.client.controller.FailureException: Fai

              led to add new connector [https]: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"JBAS

              014671: Failed services" => {"jboss.web.connector.https" => "org.jboss.msc.service.StartException in service jboss.web.connector.https: JBAS018007:

              Error starting web connector

                  Caused by: LifecycleException:  JBWEB000023: Protocol handler initialization failed"}}}}

                      at org.rhq.common.jbossas.client.controller.WebJBossASClient.addConnector(WebJBossASClient.java:176) [rhq-jboss-as-dmr-client-4.7.0.jar:4.7.

              0]

                      at org.rhq.enterprise.server.installer.ServerInstallUtil.setupWebConnectors(ServerInstallUtil.java:1276) [rhq-installer-util-4.7.0.jar:4.7.0

              ]

                      at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceImpl.java:286) [rhq-installer-util-4.7.0.jar:4.7.0]

                      at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:115) [rhq-installer-util-4.7.0.jar:4.7.0]

                      at org.rhq.enterprise.server.installer.Installer.main(Installer.java:56) [rhq-installer-util-4.7.0.jar:4.7.0]

                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_24]

                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.6.0_24]

                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.6.0_24]

                      at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_24]

                      at org.jboss.modules.Module.run(Module.java:262) [jboss-modules.jar:1.2.0.CR1]

                      at org.jboss.modules.Main.main(Main.java:329) [jboss-modules.jar:1.2.0.CR1]

              • 4. Re: RHQ 4.7 trying to bind to 8080?
                mazz Master

                Something odd was wrong in 4.6 (that was fixed in 4.7) that looked similar:

                 

                https://bugzilla.redhat.com/show_bug.cgi?id=922791

                 

                If you see anything weird with self-signed cert generation, start another forum thread on it. Make sure you let us know what "special" conditions exist on your box (are you running a JBoss app server on the same box you are installing RHQ? Did you attempt to install your own certs? Did you reconfigure rhq-server.properties to point to your own certs?, etc).