DX NetOps

  • 1.  Unable to contact DA

    Posted May 06, 2017 04:31 AM
      |   view attached

    Hi,

     

    We are using CA PM 2.5 and currently we facing problem of unable to contact for DA data source.

    Usually we just restarted the DA and it will back to normal again. But recently even if we restarted the DA, we just got this unable to contact error again in the next day. The connection between CA PC and DA is okay, there are no firewall between them. Data Collector and Data Repository services are also up.

     

    Then I checked the karaf.log and found this error message:

    ERROR | Bundle Shutdown | 2017-05-05 10:18:31,699 | RunnableTimedExecution | oncurrent.RunnableTimedExecution 109 | gframework.osgi.extender | | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=com.ca.im.aggregator.loader, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
    ERROR | esponseHandler-2 | 2017-05-05 10:18:32,024 | PolledDataReceiver | olledDataReceiver$MessageHandler 256 | .ca.im.aggregator.loader | | thread been interrupted: java.lang.InterruptedException
    ERROR | esponseHandler-1 | 2017-05-05 10:18:32,025 | PolledDataReceiver | olledDataReceiver$MessageHandler 256 | .ca.im.aggregator.loader | | thread been interrupted: java.lang.InterruptedException
    ERROR | esponseHandler-3 | 2017-05-05 10:18:32,024 | PolledDataReceiver | olledDataReceiver$MessageHandler 256 | .ca.im.aggregator.loader | | thread been interrupted: java.lang.InterruptedException

    Any suggestions about this error message?

     

    I know that CA PM 2.5 is already out of date. We are still planning to upgrade to the newest version of CA PM, but haven't got the "green light" from management. Meanwhile, does anyone ever got this error before?

     

    Thanks

     

    Regards,

    Yan

    Attachment(s)

    zip
    karaf.out.zip   104 KB 1 version


  • 2.  Re: Unable to contact DA
    Best Answer

    Broadcom Employee
    Posted May 08, 2017 03:08 AM

    Hi Yan,

     

    The error:  Closing runnable for context OsgiBundleXmlApplicationContext(bundle=com.ca.im.aggregator.loader, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

     

    indicates that there are threads in the DA process that taking too long to complete. This could be due to either resources (CPU, memory) or due to a bug that has been fixed in later releases (there are many fixes for resource handling in later releases).

     

    So apart from upgrading, take a look at how the system is using RAM and CPU when this issue occurs (use top). Its possible you may need to increase these resources.

     

    Regards

    Mohammed