DX Application Performance Management

  • Private Community
 View Only

  • 1.  Some Jboss metric is not reporting

    Posted Apr 18, 2016 02:05 AM

    Hi Team,

     

    We are using APM 9.5 version.

    Jboss server details:-Red Hat Enterprise Linux Server release 6.4 (Santiago)

    java version "1.6.0_45"

    JBOSS version - EAP6.4.5

    This metric was available before but now days we are not able to see this metric in Jboss node.

    JMX|jboss.as|deployment=sloc-webservice.ear|subdeployment=storelocator.war|subsystem=web

     

    I did below mention changes

    com.wily.introcope.agent.jmx.syncWithAllMbeanServersForcibly=true

    But i did not get any result

    Can someone please help on this ?

     

    Regards

    Vinay Nayak

    +91-8939999438

     

     

     



  • 2.  Re: Some Jboss metric is not reporting

    Broadcom Employee
    Posted Apr 18, 2016 09:58 AM

    Hi Vinay,

     

    If the metric was showing up and now it isn't, you can check a few things.

     

    1. Were there any changes made to the application?

    2. Is the investigator showing any clamp in the apm status console?  This would appear as a red ball on the top right hand corner of the investigator.

    3. Are you experiencing agents connecting/disconnecting?  If so, it could be due to a performance issue.

     

    Regards,
    Matt



  • 3.  Re: Some Jboss metric is not reporting

    Broadcom Employee
    Posted Apr 18, 2016 05:14 PM

    Hi Vinay,

    Additional to Matt's advice this may help

    There is some info on this type of problem in the wiki Troubleshooting - Agent section including checking the JBoss JMX Console:

    Agent - CA Application Performance Management - 9.7 - CA Technologies Documentation

     

    There is also a KB on that new property:

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1042397.aspx

    It is is available in 9.5.3 & 9.6 - are you using 9.5.3 agent?

    Fixed Issues -- 9.6.1, 9.6.0 - CA Application Performance Management - 9.6 - CA Technologies Documentation

    274850Issue in viewing the JMX metrics
    Synchronized JMX metrics are not visible in the investigator.

    Even though you set that property also check the agent profile still has correct JMX Filtering setup (introscope.agent.jmx.name.filter) in case something changed on app side like Matt suggested.

     

    Regards,

     

    Lynn



  • 4.  Re: Some Jboss metric is not reporting

    Posted Apr 26, 2016 06:11 AM

    Hi Lynn,

     

    Thanks for your response.I did below mention configuration but no luck.

    com.wily.introscope.agent.jmx.syncWithAllMbeanServersForcibly=true

     

     

     

    Regards

    Vinay Nayak



  • 5.  Re: Some Jboss metric is not reporting

    Broadcom Employee
    Posted Apr 26, 2016 08:40 AM

    Hi Vinay:

        Since the initial suggestions did not resolve the issue, then perhaps a case is in order.

     

    Thanks

    Hal Gernan



  • 6.  Re: Some Jboss metric is not reporting

    Posted Apr 22, 2016 01:52 PM

    Just an fyi, a typo error in 'introcope' was corrected in 96x and later to 'introscope', so

    com.wily.introcope.agent.jmx.syncWithAllMbeanServersForcibly=true to com.wily.introscope.agent.jmx.syncWithAllMbeanServersForcibly=true

     

    ref.: http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1625515.aspx



  • 7.  Re: Some Jboss metric is not reporting

    Posted Apr 26, 2016 06:06 AM

    Hi James,

     

    Thanks for correction.Still we are getting same issue there is no progress on this.

    Attached logs.

     

    $ tail -f IntroscopeAgent.sloc1.log

    4/26/16 02:19:06 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:13 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:21 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:29 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:36 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:43 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:51 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 02:19:58 AM EST [ERROR] [IntroscopeAgent.IsengardServerConnectionManager] Agent reporter thread caught unexpected exception.

    4/26/16 01:03:17 PM EST [ERROR] [IntroscopeAgent.Agent] Failed to activate JMX data collection

    4/26/16 03:16:34 PM EST [ERROR] [IntroscopeAgent.Agent] Failed to activate JMX data collection

     

    Regards

    Vinay Nayak



  • 8.  Re: Some Jboss metric is not reporting

    Broadcom Employee
    Posted Apr 26, 2016 12:45 PM

    We'll need to see the entire log in DEBUG mode to see what's happening at startup.



  • 9.  Re: Some Jboss metric is not reporting

    Posted Apr 27, 2016 04:04 PM

    You can ignore this comment of mine about the property word correction because even though I was told by our dev that the change was made, I just checked the actual code (IntroscopeProtocolAdapter.class) inside the WegbAppSupport.jar file of APM 960, 971 and 100 as I happen to handle a related support case for another customer and I notice it still contains com.wily.introcope.agent.jmx.syncWithAllMbeanServersForcibly (without an 's'). Making this note for the record. Sorry for a confusion.

    For your issue, please open a ca support case if you haven't done so yet to proceed. Thanks.