10 Replies Latest reply on Sep 4, 2012 12:10 PM by Peter Johnson

    Default port 8080 not working

    shawn aslam Newbie

      Application was working fine on port 8080 on the jboss version jboss-5.1.0.GA, and for some reason we have to start the server today and after that jboss is not listening on port 8080.

      I dont know what to check as by default it should listen on 8080 port. Can anyone tell me what I need to do other than starting the jboss service?

        • 1. Re: Default port 8080 not working
          Peter Johnson Master

          Were there any error messages in the server.log? Have you tried running netstat to see if something else is using port 8080? (This might help on that last question: https://community.jboss.org/wiki/DebugBindException) Also, which OS?

          • 2. Re: Default port 8080 not working
            shawn aslam Newbie

            After psoting i checked and found 1098 port is in use. I killed the PID using this port but still getting the same error and netstat is not showing 1098 port how amazing.

            What should I do now by the way I am using windows server and Jbos 5.1.0 GA

            • 3. Re: Default port 8080 not working
              Peter Johnson Master

              Why did you kill the process using port 1098? Yes, that is the port mentioned in the wiki page I mentioned, but the general message of that page is how to debug the port binding error that you are getting (port 1098 just happens to be a common port that has issues.) You, on the other hand, are having issues with port 8080. Did you look in the server.log to see exactly what errors you are getting? You need to post those error stacks first. The issue might not even have anything to do with ports!

              • 4. Re: Default port 8080 not working
                shawn aslam Newbie

                Peter basically there is  no issue with 8080 as jboss was not started so i was not able to hit on 8080 so i thought issue was 8080 port. Basic cause was jboss was not started and log saying 1098 port already in use.

                I hope it clarifies.

                • 5. Re: Default port 8080 not working
                  Peter Johnson Master

                  Are there any errors in the server log at this point?

                   

                  What does netstat show? Which ports are in use by the java process that is running JBoss AS?

                  • 6. Re: Default port 8080 not working
                    shawn aslam Newbie

                    here is the

                    first exception in the server.log file

                    2012-09-04 10:38:32,543 INFO  [org.jboss.web.WebService] (main) Using RMI server codebase: http://md-dmz-www:8083/

                    2012-09-04 10:38:32,839 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss:service=Naming state=Create mode=Manual requiredState=Installed

                    java.rmi.server.ExportException: Port already in use: 1098; nested exception is:

                        java.net.BindException: Address already in use: JVM_Bind

                        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)

                        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)

                        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)

                        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)

                        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)

                        at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)

                        at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)

                        at org.jnp.server.Main.initJnpInvoker(Main.java:462)

                        at org.jnp.server.Main.start(Main.java:422)

                        at org.jboss.naming.NamingService.startService(NamingService.java:320)

                        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)

                        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)

                        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                        at java.lang.reflect.Method.invoke(Method.java:597)

                        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

                        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

                        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)

                        at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

                        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)

                        at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

                        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

                        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

                        at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)

                        at $Proxy38.start(Unknown Source)

                        at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)

                        at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)

                        at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)

                        at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)

                        at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

                        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

                        at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)

                        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

                        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

                        at org.jboss.system.ServiceController.doChange(ServiceController.java:688)

                        at org.jboss.system.ServiceController.start(ServiceController.java:460)

                        at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)

                        at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)

                        at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)

                        at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

                        at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

                        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

                        at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

                        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

                        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)

                        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

                        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

                        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

                        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

                        at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

                        at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)

                        at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

                        at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

                        at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

                        at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

                        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

                        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

                        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

                        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

                        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

                        at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

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

                        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.net.BindException: Address already in use: JVM_Bind

                        at java.net.PlainSocketImpl.socketBind(Native Method)

                        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)

                        at java.net.ServerSocket.bind(ServerSocket.java:328)

                        at java.net.ServerSocket.<init>(ServerSocket.java:194)

                        at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:124)

                        at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:99)

                        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)

                        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)

                        ... 76 more

                    • 7. Re: Default port 8080 not working
                      Peter Johnson Master

                      Now some of you earlier comments make more sense. I could not understand whay you said "still getting the same error" and also said "netstat is not showing 1098 port". Try using tcpview and see if that gives you a better idea of which process is using port 1098. You do have to find this out and stop that process before you can go on.

                      • 8. Re: Default port 8080 not working
                        shawn aslam Newbie

                        Tcpview is also not listing 1098 port.

                        it seems the problem i am facing is in the below thread

                        http://www.danielschneller.com/2006/09/windows-tcp-port-conflicts-above-1024.html

                        but even after reserving port 1098-1099 I am unable to get rid of this error.

                        • 9. Re: Default port 8080 not working
                          shawn aslam Newbie

                          I got the solution I change the RMI port from 1098 to 2001 in bindings-jboss-beans.xml and its working.

                          • 10. Re: Default port 8080 not working
                            Peter Johnson Master

                            Try starting Jboss AS from the command line and see if that works.

                             

                            I'm wondering is this is a security-related issue? What credentials are being used for the JBoss service?

                             

                            I seem to recall a post a long time back that had the same issue you are describing - a binding error but it appeared that nothing was using the port in question. I don't recall what the solution was. I'll see if I can find the post. You could also reach for "port binding 1098" in the forums, see what other posts turn up.