DX Application Performance Management

Expand all | Collapse all

JMX Enabling

  • 1.  JMX Enabling

    Posted Jul 25, 2012 12:45 PM
    Hi,
    I need to enable JMX metrics collection on standalone jvm's without an app server. The JVM's are communicating through Tibco EMS messaging. Looking at the Java Agent documentation there are no clear instructions to do so in a non app server environment.

    I have already enabled the
    1) introscope.agent.jmx.enable=true
    2) introscope.agent.jmx.name.primarykeys=

    How do i find the identifier for MBeans. For now i have kept it empty and also the filter property is empty.

    Please let me know the steps i should follow to enable this.

    Thanks
    Sachin


  • 2.  RE: JMX Enabling

    Broadcom Employee
    Posted Jul 25, 2012 01:39 PM
    You can disable item 2 for the time being while you work out your filter.
    As long as you instrument the startup of the JVM properly, you should see the MBeans under your agent in the Investigator.

    [list]
    [*]Are you using the default or allappserver Java agent?
    [*]Are you using the SOA extension for Tibco EMS?
    [list]


  • 3.  RE: JMX Enabling

    Posted Jul 25, 2012 02:40 PM
    1. I am using the default Java Agent

    2. For the agent, I have the following set in the JVM properties. Do I need to add any additional flags to enable JMX?

    -javaagent:"${WILY_HOME}Agent.jar" -Dcom.wily.introscope.agentProfile=${WILY_HOME}core/config/IntroscopeAgent.profile


    It is picking up the other metrics, but just miising the JMX folder.

    Thanks
    Sachin


  • 4.  RE: JMX Enabling

    Posted Jul 25, 2012 02:49 PM
    Currently, I believe JMX metrics are only retrieved from agents that are running in an Application Server, e.g. Tomcat, WebLogic, WebSphere. There is a JMX_Agent field extention available in the Community Documents that can be run as a second -javaagent startup argument to work-around this behavior, but I have never tried it.


  • 5.  RE: JMX Enabling

    Broadcom Employee
    Posted Jul 25, 2012 03:07 PM
    You can pickup MBeans from any MBean Server if it's complies with the Java standard.

    I think the problem here is that he still needs to include WebAppSupport.jar to the classpath. This was discussed previously in a recent post.


  • 6.  RE: JMX Enabling

    Posted Jul 25, 2012 04:12 PM
    I looked at some of the other post talking about WebAppSupport.jar. Where do i find this jar?


  • 7.  RE: JMX Enabling

    Broadcom Employee
    Posted Jul 25, 2012 03:04 PM
    For TIBCO EMS, please follow the instructions I posted previously on monitoring that.

    Once you have that configured gathering data, reply back and let us know if you still need the JMX data. I think you'll get what you need from the EMSAgent.


  • 8.  RE: JMX Enabling

    Posted Jul 25, 2012 04:15 PM
    EMS Agent I believe will provide me statistics on Queues. But for the actual standalone JVM's i would need the JMX metrics in Wily.


  • 9.  RE: JMX Enabling

    Broadcom Employee
    Posted Jul 25, 2012 06:23 PM
    <AGENT_HOME>/common/WebAppSupport.jar


  • 10.  RE: JMX Enabling

    Posted Jul 26, 2012 03:58 PM
    Here is what you need to do for JMX enabling

    - run your app with -Dcom.sun.management.jmxremote as a java param
    - ensure jmx ppty is set to true in your profile
    - copy WebAppSupport from common to core/ext

    restart your app


  • 11.  RE: JMX Enabling

    Broadcom Employee
    Posted Jul 25, 2012 01:52 PM
    Instructions for installing and monitoring TIBCO EMS is located in the SOA Implementation Guide, "Monitoring TIBCO Enterprise Message Service".