2 Replies Latest reply on Apr 15, 2002 11:46 PM by mikefinn

    "Could not start on port 1099" when start JBoss3.0 downloade

    qwang

      Hi,

      I checked out jboss-all today and built it on my machine. When I started it, I got the following messages, event after I restarted my PC:

      ...........

      11:15:00,604 INFO [WebService] Started webserver with address: null port: 8083
      11:15:00,615 INFO [WebService] Codebase set to: http://su106962:8083/
      11:15:00,615 INFO [WebService] Started
      11:15:00,615 INFO [NamingService] Starting
      11:15:00,625 INFO [NamingService] Starting jnp server
      11:15:00,725 ERROR [NamingService] Could not start on port 1099
      java.net.BindException: Address in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405)
      at java.net.ServerSocket.(ServerSocket.java:170)
      at org.jnp.server.Main.start(Main.java:200)
      at org.jboss.naming.NamingService.startService(NamingService.java:155)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
      62)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
      nDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
      ler.java:867)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:341)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
      nDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:281)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:665)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:507)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:470)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:452)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
      nDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:320)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:218)
      at org.jboss.Main.boot(Main.java:142)
      at org.jboss.Main$1.run(Main.java:375)
      at java.lang.Thread.run(Thread.java:484)
      11:15:00,875 INFO [NamingService] Listening on port 1099
      11:15:00,875 INFO [NamingService] Started
      11:15:00,885 INFO [JNDIView] Starting
      11:15:00,885 INFO [JNDIView] Started
      11:15:00,885 INFO [SecurityConfig] Starting
      11:15:00,895 INFO [SecurityConfig] Started
      11:15:01,025 INFO [JaasSecurityManagerService] Starting
      11:15:01,035 INFO [JaasSecurityManagerService] Started
      ..............

      Dose anyone knows the reason of it and how to get rid of this message?

      Thanks.

      qwang



        • 1. Re: "Could not start on port 1099" when start JBoss3.0 downl
          mcacker

          are you running netscape? i have this problem running netscape and/or IM, it seems to use the default rmi port 1099. the only solution i can find to this problem is to stop netscape when running jboss. i attempted to reconfigure jboss/jndi to use a different port, but there appears to be a problem there - see earlier post that noone seems able to tell me how to fix.

          hope this helps, Mitchell.

          • 2. Re: "Could not start on port 1099" when start JBoss3.0 downl
            mikefinn

            Yeah - something is on 1099. Do a:
            "netstat -a | grep 1099" and you'll see. I don't have any probs with IM (aim on Win), but don't know about NS - I use 4.7.x w/o probs.

            FWIW - If you want to see what process is listening, it's much easier in *nix. Some netstats allow --programs (some Linuxes do), or you'll need lsof. Windows? Stop services and nuke processes until it works....

            Mike