3 Replies Latest reply on Nov 30, 2011 12:55 PM by while_true

    Hi All

    bhadraiah

      Q: How to avoid the jmx connector port conflict issue while running the multiple jboss servers on a machine?

       

           Error shown in console as:

           Error in server:

           DEPLOYMENTS IN ERROR:

           Deployment "JBOSS_HOME/jboss-5.1.0.GA/server/default/deploy/jmx-remoting.sar/" is in error due to the following     reason(s): java.rmi.AlreadyBoundException: jmxconnector

       

      Solution is required very urgent, for any better approach than that of changing the default port number to some other port.

       

      Please have a look on this urgent issue need to fix.

       

      Thanks in Advance!

       

      Regards,

      Bhadri

        • 1. Re: Hi All
          while_true

          Hey Bhadraiah,

           

          You might want to take a look at this article http://community.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine or this other one http://community.jboss.org/wiki/ServiceBindingManager.

           

          Grateful for your attention.

           

          Best regards.

          1 of 1 people found this helpful
          • 2. Re: Hi All
            bhadraiah

            Thanks a lot Antonio,

            Nice helpful answer but i have used already that -b option while starting the app server. than also i am getting conflict issue for jmx server.

            Here is my jboss server with that issue is pointing at "JBOSS_HOME/jboss-5.1.0.GA/server/default/deploy/jmx-remoting.sar/ : java.rmi.AlreadyBoundException: jmxconnector

             

            Highly appreciate the best solution!! for with out changing default port number to some other is there any other approach?

             

            Thank you,

            Bhadraiah

            • 3. Re: Hi All
              while_true

              Bhadraiah,

               

              I've found another article that I think suits your purposes. It address the modification of the range of ports for each JBoss service and I think that's what you need.

               

              Please, check this out: http://community.jboss.org/wiki/ConfigurePorts

               

              Adding -Djboss.service.binding.set=ports-01 after your run command the ports of your new JBoss instance get an increment of 100 therefore the already bound exception shoudn't occur!

               

              Message was edited by: António Ribeiro