IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Some features are not working

You might have met the situation that some feature are not working. The following content provides solutions to this situation.


ITCAM "Cancel Thread" feature does not work

The problem: Clicked "Cancel Thread" on the thread (Web Container thread in this case) and found it still shows with all the thread list that is not cancelled.

The cause: "Cancel Thread" feature of ITCAM may not always able to immediately terminate Java threads running native code. This is a limitation of JVM.

In any event, the cancelling of live threads is a dangerous practice, and should be used with care and discretion.

The solution: If the "Cancel Thread" feature of ITCAM is used to terminate a Java thread running native code, that thread will continue to run until either of the following events occur:

If neither of these events occurs, the thread will continue to run until it returns from native code back to Java code and only then it will be terminated.

If the thread does not return from native code back to Java code (for example as a result of a hang or loop in the native code), restarting JVM may be needed to reclaim the thread.


Service Integration Bus (SIB) monitoring not working

The problem: In WebSphere, Performance Monitoring Infrastructure (PMI) for SIB is not configured and therefore no SIB data is collected.

The reason: SIB PMI data settings cannot be saved in the WebSphere configuration.

The solution: Adjust SIB PMI settings as runtime parameters by following these steps:

  1. If the DC_home/runtime /<app_server_version>.<node_name>.<server_name>/custom /datacollector_custom.properties file does not yet exist, create one.

  2. In the datacollector_custom.properties file, add the following lines:
    am.was6custompmi.settings.1=SIB Service=*
    am.was6custompmi.settings.2=SIB Service=*
    am.was6custompmi.settings.3=SIB Service=*
    These lines set custom PMI settings for L1, L2 and L3 monitoring levels.

  3. Restart the application server.


Parent topic:

All platforms

+

Search Tips   |   Advanced Search