6 Replies Latest reply on Apr 10, 2009 10:13 AM by ubhole

    JConsole cannot connect to fuse esb 4

    thygesen

      When I start Jconsole I see a local process: "org.apache.servicemix.kernel.mail.Main" but cannot connect to it. Gets a timeout.

       

      Running Fuse ESB 4.0.0.4 on Windows XP

      featuresBoot=management,transaction,activemq,camel

       

      \peter

        • 1. Re: JConsole cannot connect to fuse esb 4
          ubhole

          Can you specify what JDK version you are using? I tried it on clean install and then later changing featuresBoot to all 4 you specified and both case connected properly with JDK 1.5.0_13.

           

          Ulhas

          • 2. Re: JConsole cannot connect to fuse esb 4
            thygesen

            I running jdk 1.6.0_10

             

            /peter

            • 3. Re: JConsole cannot connect to fuse esb 4
              ubhole

              Just tried on latest JDK 1.6.0_13 and it's showing up correctly. Do you have anything deployed? Can you try stopping fuse esb 4, cleaning up data directory and restarting esb again?

               

              /Ulhas

              • 4. Re: JConsole cannot connect to fuse esb 4
                thygesen

                Yes I have deleted the data folder several times with out any effect.. but right now I managed to connect!! for the first time.. very strange.

                 

                Can it be that its using some port that might have been taken by another program/process the other times i hvae tried? e.g. 1099,, which i have had problems with before... using e.g. synapse.

                 

                /peter

                • 5. Re: JConsole cannot connect to fuse esb 4
                  thygesen

                  Annoying!! Now I cannot connect again... something must be blocking..

                   

                  /Peter

                  • 6. Re: JConsole cannot connect to fuse esb 4
                    ubhole

                    Annoying!! Now I cannot connect again... something must be blocking..

                    Can you do netstat and see if port 1099 is listed? Also, if you are can run tcpview you can see which process is using port 1099.

                     

                    Other option you can try is to change JMX port and URI in etc/

                    org.apache.servicemix.management.cfg file like following example

                     

                    rmiRegistryPort = 1299

                    jmxLogin        = smx

                    jmxPassword     = smx

                    serviceUrl = service:jmx:rmi:///jndi/rmi://localhost:1299/jmxrmi

                    daemon          = true

                    threaded        = true

                    objectName      = connector:name=rmi

                     

                     

                    Ulhas