5 Replies Latest reply on Nov 2, 2004 12:43 AM by bershath27

    Installing JBoss 4.0.0 on Windows XP Professional

    bershath27

      I have a problem in installing JBoss 4.0.0 on windows XP professinal license machine. what happens is the server throws an exception (see below).

      is there any solution for this issue?? i have tried to start the server with both jdk 1.5.0 and also with the jdk 1.4.2, but got the same failure message.

      and also i have tried changing the RMI port by giving different values. but on the same machine JBoss 3.2 works ok, can somebody help me pls?

      thanks in advance.
      jerome


      jboss.web:service=WebServer
      2004-11-01 17:20:28,948 INFO [org.apache.catalina.startup.Embedded] Catalina naming disabled
      2004-11-01 17:20:29,807 ERROR [org.apache.coyote.http11.Http11Protocol] Error initializing endpoint
      java.net.BindException: Address already in use: JVM_Bind:1098
      at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
      at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137)
      at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429)
      at org.jboss.web.tomcat.tc5.StandardService.initialize(StandardService.java:688)
      at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
      at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
      at org.apache.catalina.startup.Catalina.start(Catalina.java:548)
      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:324)
      at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
      at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
      at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:324)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:416)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
      at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:416)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)

        • 1. Re: Installing JBoss 4.0.0 on Windows XP Professional
          luc.texier

          Looks like Tomcat service is trying to start on port 1098, thus conflicting with the RMI port of the naming service.

          Look into
          /deploy/jbossweb-tomcat50.sar/server.xml
          and check that the connector is listening on port 8080

          Also, make sure that you don't any stale instances of JBoss running in the background.

          • 2. Re: Installing JBoss 4.0.0 on Windows XP Professional
            bershath27

            No, i tried all the possibilities that you have stated. and also am not running any service on the port which jboss complains that i'm using. and on this machine i have never installed JBoss beore or any previous version or Apache, Tomcat, IIS or any services.

            pls help me on this.
            thanks
            jerome

            • 3. Re: Installing JBoss 4.0.0 on Windows XP Professional
              bershath27

              further... i tried to install and run Jboss on another two XP machines... they gave me the same results. one of the machines been upgraded with the service pack 2, still failed to start the JBoss server.


              but on all the machines, JBoss 3.2 works fine...

              thanks
              jerome

              • 4. Re: Installing JBoss 4.0.0 on Windows XP Professional
                anil.saldhana

                Why don't you run tomcat on a port other than 8080 and check if it works? Go to server.xml under deploy/jbossweb-tomcat50.sar directory and replace 8080 with 8081.

                Some service on your box is using up port 8080.

                • 5. Re: Installing JBoss 4.0.0 on Windows XP Professional
                  bershath27

                  Ok, found the solution at last. changing ports wont do any better. because the windowz keep on blocking the port on which your RMI uses.

                  Problem

                  this happens when you have activated the windoez personal firewall(??). when this is on, windows keep on blocking the RMI port blindly(as usual) though there's no harm with it.

                  Solution

                  you have to disable the personal firewall (which is good for nothing) from the control panel. then restart the jboss server.. works ok...

                  Advanced

                  actually there's no collision with the catelina for the Jboss disable catelina NAMING before he opens the RMI port.

                  thanks for your valued time and efforts in helping me out.

                  jerome (tyronne w)