10 Replies Latest reply on Aug 31, 2011 10:53 AM by Chris Nash

    Can't access web management console

    Chris Nash Newbie

      Hi,

       

      I used the latest jbpm-installer and ran the demo. Eclipse tooling works fine, but I can't access the web management console (http://localhost:8080/jbpm-console). I get a 404 error. I don't really know how to troubleshoot this. Going to http://localhost:8080/ gives me an error message and a stack dump -- not very helpful. Anyone know anything I can try? I started a session via "ant start.demo", and JBoss is running, as is h2 and human.task. Would the fact that I'm running it on Windows Server 2003 have anything to do with it?

       

      Thanks in advance!

       

      EDIT: In the boot.log, I found this error:

       

      Failed to build ManagedDeployment for: AbstractKernelDeployment@1455cf4{name=file:/C:/jbpm-installer/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@d9b071{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]}

      org.jboss.deployers.spi.DeploymentException: Error deploying: file:/C:/jbpm-installer/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml

          at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

          at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:433)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)

          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

          at org.jboss.Main.boot(Main.java:221)

          at org.jboss.Main$1.run(Main.java:556)

          at java.lang.Thread.run(Thread.java:662)

      Caused by: java.lang.IllegalStateException: ClassLoader has not been set

          at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)

          at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)

          at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)

       

      I don't know how serious it is, but that's the only thing close to an error I could find. What next?

        • 1. Re: Can't access web management console
          Tihomir Surdilovic Master

          AFAIK this is just a DEBUG level message. Do you see anything in the server logs? Maybe something happenend during the download of jboss as..you could try to:

          - go to $jbpm_installer_dir/lib and remove jboss-5.1.0.GA.zip

          - go to $jbpm_installer_dir and run "ant clean.demo", then "ant install.demo" ..this should download the AS again

          - run "ant start.demo" ... and watch the server logs in $jbpm_installer_dir/jboss-5.1.0.GA/server/default/logs/ (server.log)

           

          Hope this helps.

          1 of 1 people found this helpful
          • 2. Re: Can't access web management console
            Chris Nash Newbie

            Digging in the server log, I found this:

             

             

            So clearly something else is already using port 8080 (what is, I have no idea, it's a completely clean system, new OS install). So I guess I have to dig around and either (a) try to find what's using 8080 and shut it down or (b) move the server process to another address. Option (b) might be easier if I can find where to configure jBPM.

             

            Thanks for the help!

            • 3. Re: Can't access web management console
              Tihomir Surdilovic Master

              >> Digging in the server log, I found this: <<

              I cannot see any stack strace below that. Maybe if you are on windows try "netstat -a -b", it's been a while since I used windows so "netstat -help" could confirm .

               

              Thanks.

              1 of 1 people found this helpful
              • 4. Re: Can't access web management console
                Chris Nash Newbie

                Sorry, forgot to insert stack trace:

                 

                ERROR [org.apache.coyote.http11.Http11Protocol] (main) Error initializing endpoint

                java.net.BindException: Address already in use: JVM_Bind localhost/127.0.0.1:8080

                    at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:504)

                    at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)

                    ...

                • 5. Re: Can't access web management console
                  Chris Nash Newbie

                  Okay, that's weird. "netstat -n" doesn't show anything runnning on 127.0.0.1:8080 (neither does "netstat -a -b"), but that's where JBoss fails.

                  • 6. Re: Can't access web management console
                    Tihomir Surdilovic Master

                    Do you have some firewall client running on your machine? If so, stop it. These types of issues are tricky on windows. AFAIK if you look deeper into your server logs JBoss should have found another port most likely to run on other than 8080.

                    • 7. Re: Can't access web management console
                      Chris Nash Newbie

                      There is a corporate firewall running, but nothing on local machine (AFAIK). JBoss didn't find--actually didn't even look for--another port to run on. After a 130 line stack trace, it displays another error:

                       

                      ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=WebServer state=Create

                      LifecycleException:  Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind localhost/127.0.0.1:8080

                          at org.apache.catalina.connector.Connector.initialize(Connector.java:1031)

                          at org.apache.catalina.core.StandardService.initialize(StandardService.java:683)

                          at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:821)

                       

                      Which looks like a direct result of the previous error. Near the end of the log, these message are displayed:

                       

                      ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                       

                      DEPLOYMENTS MISSING DEPENDENCIES:

                        Deployment "jboss.web.deployment:war=/ROOT" is missing the following dependencies:

                          Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")

                        Deployment "jboss.web.deployment:war=/admin-console" is missing the following dependencies:

                          Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")

                       

                      It goes on like that for awhile, but doesn't improve. So I don't think it's finding another port.

                       

                      Well, I'm not an expert at this webserver stuff. Just trying to get the components to run...

                      • 8. Re: Can't access web management console
                        Tihomir Surdilovic Master

                        Do you have anything else running, like maybe another Tomcat on your machine? Something else has already claimed the port number or your OS is not allowing it to be used. If you google your errors there are tons of forum posts around parts of your logs...maybe some of them could help.

                        • 9. Re: Can't access web management console
                          Chris Nash Newbie

                          I shouldn't have anything else running. Netstat didn't find anything and I just installed this OS, so it shouldn't have anything running in the background, apart from what Windows throws out there. I'll keep looking on the Internet, but it really baffles me that this is the second machine I've tried it on without getting it to work.

                          • 10. Re: Can't access web management console
                            Chris Nash Newbie

                            The logs were a big help. I moved JBoss to connect to port 8090 as opposed to the default 8080 and that solved the problem. Some ohter service was running on 8080 (and it didn't show up on netstat). Thanks for all the assistance!