Announcement Announcement Module
Collapse
No announcement yet.
jconsole remote server connection Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • jconsole remote server connection

    I am getting started with jmx to my application , I am using spring jms server, here is my configration


    Code:
    <context:mbean-export/>
    <bean class="org.springframework.jmx.support.MBeanServerFactoryBean"/>
    
    <bean id="jemosJmxServer" class="org.springframework.jmx.support.ConnectorServerFactoryBean" depends-on="rmiRegistry">
    <property name="objectName" value="connector:name=rmi" />
    <property name="serviceUrl" value="service:jmx:rmi://localhost:9999/jndi/rmi://localhost:10099/myConnector" />
    </bean>
    
    <bean id="rmiRegistry" class="org.springframework.remoting.rmi.RmiRegistryFactoryBean">
    <property name="port" value="10099" />
    </bean>
    when I deploy my application to my local server, use jconsole I can see all my mbeans I can call methods on the benas etc.. all works good.
    when deployed to remote server a linux box, use jconsole the connection succeeds , but none of my mbeans are visible ,please advice me what I have to do for connection to my jmx server deployed in remote server.

  • #2
    I tried other thing when I deploy in jetty I can use jconsole see my mbenas and when I deploy in weblogic none of my mbeans are visibel , please advice me do I have to change anything in weblgic startup script to make me mbeans visible ?

    Comment


    • #3
      I am also confuse about it!

      Comment


      • #4
        Try putting <context:mbean-server /> before the export line. I think that will try to connect to the default mbean server if one is found.

        Comment


        • #5
          M beginner and things mentioned are bit advanced....!!!!

          Any clear explanation will be helpful....!!!!

          Comment


          • #6
            this may a bit late reply but anyway :
            some servers do not allow you to register your mbeans under an arbitrary domain name,
            you should provide a domain name when registering your mbeans

            Comment

            Working...
            X