DX Application Performance Management

 View Only

Top 20 APM, ASM, Executive Insight KBs for July 2015

  • 1.  Top 20 APM, ASM, Executive Insight KBs for July 2015

    Broadcom Employee
    Posted Aug 21, 2015 05:17 PM

    1. When using Java 1.7 u71 or Java 1.8 u25 on the client desktop, the Webstart Workstation fails to start and no error messages are reported. TEC1936395.

    Description: Using a Java 1.7 u71 or Java 1.8 u25 client desktop has workstation Webstart launch issues. After launch, the usual Java install jar and the trust the publisher prompt appears. However the Workstation does not start and no error messages are displayed. 




    2. When do we have to use the flag XX:-UseSplitVerifier ? Why is this needed? TEC600823 

    Description: Use of the flag XX:-UseSplitVerifier



    3.Using Web Start Workstation with Java 7 u51 (Java7u51, Java 1.7.0_51-b13) TEC606706

    Description: A Technical Advisory has been issued to address problems starting the APM Web Start Workstation. The Advisory allows users to run the Web Start workstation with Java 7 u45, but does not work with Java 7 u51. This article updates the Advisory to allow users to run the Web Start workstation with the enhanced security present in Java 7 u51 and above by taking the additional step of reducing the Security Level from High to Medium.



    4.How to Configure CA APM to use LDAP Authentication (Introscope and APM CE) TEC595290

    Description: CA APM gives you choices for securing and authorizing access to some or all of the features and domains of the Enterprise Manager and Workstation. Using LDAP, you can authenticate user and group access with CA APM while maintaining user and group authorization in local configuration files.

    There are 3 ways to secure CA APM

    Local  - Users and groups are both authenticated and given authorization via local configuration files maintained on the Enterprise Manager server.

    LDAP  - Users and groups are authenticated by LDAP directories but authorized by local configuration files maintained on the Enterprise Manager server or CA EEM.

    EEM  - Users and groups are both authenticated and authorized by a CA EEM (CA Embedded Entitlements Manager) server for CA APM activities.

    This article discusses how you can integrate CA APM with your own LDAP directory for authentication to the APM Workstation and Enterprise Manager.


    5.Could not initialize class sun.awt.X11GraphicsEnvironment error during APM 9.5 install. TEC601075

    Description: Red Hat Linux 2.6 Fresh install of 9.5 MOM 64bit, 24 GIG Memory

    When running installer in console mode, we see an error below and are unable to complete the install:

    Status: FATAL ERROR Additional Notes: FATAL ERROR - The Installer has failed due to an Unhandled Exception java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment.


    6.MQ Message Broker Error: AMQ9999: Channel program ended abnormally Channel program SYSTEM.DEF.SVRCONN terminated abnormally  TEC604907
    Description: This article applies to APM for IBM WebSphere MQ

    APM appears to occupy all SYSTEM.DEF channels without releasing them. Eventually, all channels are consumed.

    The following error is observed in the MQ logs:
    • 05/28/14 14:57:08 - Process(1187934.147) User(mqadm) Program(amqrmppa) AMQ9999: Channel program ended abnormally.

    Channel program SYSTEM.DEF.SVRCONN terminated abnormally





    7.Why are WebSphere nodes in a cluster failing to start, even if one node is not instrumented? TEC614151 

    Description: The IBM Class Sharing feature, which is enabled out of box, causes classes to be stored locally. The classes could contain bytecode instrumented by the Agent. So even if the Agent is removed, those references are still loaded and can cause startup issues. This article addresses how to resolve this issue and what can be done to configure Class Sharing properly.


    8.Technical Advisory: Workstation Web Start Client Fails to Start with Java 7 Update 45 (Java 1.7.0_45), Java 6 Update 65 (Java 1.6.0_65), and Java 5 Update 55 (Java 1.5.0_55) TEC603806

    Description: CA Technologies has identified a potential issue with the CA APM/Introscope Workstation Web Start client with Java 7 Update 45 (Java 1.7.0_45), Java 6 Update 65 (Java 1.6.0_65) and Java 5 Update 55 (Java 1.5.0_55). This technical advisory describes the affected versions and platforms in more detail, and explains the workarounds or remediation actions that are recommended to prevent this issue from impacting your usage of CA APM.



    9.How to set up JBoss 6 EAP with the Introscope Agent and see JMX metrics  TEC606597 


    This article discusses how to set up the Introscope Agent with JBoss 6 EAP and see JMX metrics. Please note that instructions for JBoss 7 AS differ and are addressed in a separate Technical Document.

    10. JMX in Jboss 7.x / jboss eap 6.x  TEC1042397 

    Description: You notice that the agent is unable to identify newly added MBeans to the MbeanServer. This issue is related to bug in JBOSS Appserver, CA technologies has already reported the issue to Redhat. In the meantime, we have made a code change in the CA Agent side to be able to handle this scenario : Enhancement#274850


    11.How to implement CA EEM and LDAP for Authentication and Authorization of CA APM

    Description: Using CA EEM, CA Embedded Entitlements Manager, in conjunction with a supported LDAP Server, it is possible to eliminate manual updates to CA APM configuration files every time you need to add a new user, change a password or update access permissions.

    CA EEM allows you to utilize a supported LDAP server for authentication while it controls authorization policies for LDAP users and groups. If you do not use LDAP, EEM can even perform authentication duties using the secure, proprietary CA Directory, which is included.

    CA EEM is bundled with CA APM and is available from the APM Product Downloads Page on support.ca.com. It can be installed on the same or a separate server as the Enterprise Manager.. CA EEM supports many CA products, serving as a single point of control for authentication and authorization.



    12. APM Cluster Performance Health Check  TEC604648

    Description: The Perflog can reveal much about the health of the Collectors in a cluster. This article discusses the most easily diagnosed issues. For a complete analysis, CA Services should be engaged for a comprehensive health check.



    13.WASX7015E ADMN0022E errors when running listServers script to enable WebSphere agents for instrumentation. javax.management.JMRuntimeException TEC604647

    Description: The listServers scripts can be used to automate configuration of multiple Websphere instances for Introscope monitoring.

    This is one possible error that you may see when running the command:

    WASX7015E: Exception running command: "listServers D:\\CA\\Wily"; exception


    javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getState operation on Server MBean because of insufficient or empty credentials.



    14.MQ Agent cannot connect to MQ Server. ssl handshake failure. Reason code 2397 MQRC_JSSE_ERROR TEC606483

    Description: The MQ Agent fails to connect to the MQ Server when using SSL set to Required Client Authentication.

    When the SSL channel is configured for non-required client authentication, it allows full connectivity, but when the channel is set to required client authentication the connection fails.

    Note that the functionality works even when not using SSL.

    When SHA or MD5 is configured on channel APM.SSL.SVRCONN, the Client/MQ server connection negotiation throws a JSSE exception. This occurs even when the MQ server certificate has been added to the client and the client certificate has been added to the server.

    The following messages are logged in the Agent Log:

    ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.TracerDriverThread] MQMonitor: For configuration instance MQAPMTST@test_dev_machine and the drivers(namelist,cluster) an error occurred in sending query to MQ. The target MQ (test_dev_machine:port#) may be down. Reason code 2397 MQRC_JSSE_ERROR

    $ openssl s_client -connect test_dev_machine :port# -prexit CONNECTED(00000003)

    14815:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:188



    15. Getting "Out of Shared Memory" Errors for Postgres database TEC1920756

    Description: The Postgres APM database is seeing "Out of Shared Memory Errors." What can be done about this?



    16. A Guide to Solving Common Stats and Defects Aggregation Problems TEC610521 

    Description: This tech note is an expansion of Stats Aggregation Issue after Upgrading from 9.0.x to, by Michal Lehotsky. The original document discusses ways to detect if statistical aggregation is not working and how to correct it.


    17. Getting the Application Server error: java.lang.ClassNotFoundException: com.wily.introscope.api.weblogic.IntroscopeStartupClass  TEC614778 

    Description: What is causing the error below in the WebLogic server log on starting Weblogic/APM Agent?

    Failed to invoke startup class "Introscope Startup Class", java.lang.ClassNotFoundException: com.wily.introscope.api.weblogic.IntroscopeStartupClass 
    java.lang.ClassNotFoundException: com.wily.introscope.api.weblogic.IntroscopeStartupClass 
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200) 
    at java.security.AccessController.doPrivileged(Native Method) 
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)



    18. What to do when Introscope Standalone Workstation Thick Client in Windows 7 won't launch.  TEC606482

    Description: When attempting to run the thick workstation client on Windows 7 or similar environments, you may encounter the following:
    • Nothing happens when selecting Introscope Workstation from Windows Programs Menu

    • Nothing happens when clicking Introscope_Workstation.exe from Windows Explorer

    • No errors or warnings are reported in Windows Event Application Logs


    19. Why does the “LaunchAnywhere either could not find a Java VM…..”  message appear in the IntroscopeEnterpriseManagerSupport.log? TEC1576694

    Description: This article explains why the message “LaunchAnywhere either could not find a Java VM...” appears in the support log. This is because this message is an explicitly defined property in the Introscope_Enterprise_Manager.lax file.



    20.Smartstortools Help TEC609741

    Description: Best practices and examples for Smartstortools usage.