APM Top 20 Accessed KB Articles for March 2015
1. GHOST Vulnerability and TIM TEC1761946 http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1761946.aspx
Description:This is a statement about recent security vulnerabilities and how to fix them in the various versions.
2.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)
3. Smartstortools Help TEC609741
Description:Best practices and examples for Smartstortools usage.
4. Information about com.wily.introscope.agent.simpleInstanceCounter.referenceTrackingLimit TEC547492
Description:This is information about the usage of the com.wily.introscope.agent.simpleInstanceCounter.referenceTrackingLimit, introduced in APM 9.0.5.
When monitoring instance counts, the following error may occur:
[WARN] [IntroscopeAgent.Agent] SimpleInstanceCounter: while tracking instances of typecom.mycompany.myclass, too many instances are being tracked in a short interval. Clamp limit of 25000 has reached and tracking new instances will stop. To raise clamp limit, add property com.wily.introscope.agent.simpleInstanceCounter.referenceTrackingLimit
5. CA Wily Technical Advisory: Native Memory Leak on IBM Java 1.6 when using -javaagent TEC576360
Description:October 2011 - CA Wily has become aware of a potential issue on IBM Java 1.6 where an application under management may experience severe native memory overhead. This technical advisory describes the affected versions and platforms in more detail, and explains what remediation actions are recommended.
6. JMS Webservices invocations messages placed on JMS queues (TIBCO EMS queues) are big and it takes a lot more time than the expected to be processed. TEC595968
Description: Whenever a single running BW process invokes a HTTP or JMS Webservice willy adds a CorID field to SOAP/HTTP/JMS headers and keeps on incrementing its size for each invocation made within that process. This produces big messages in which the body has around 1000 bytes and the header 9000 bytes, due to this CorID field.
You try to remove this field in SOAP and HTTP headers by adding the following lines to IntroscopeAgent.profile file:
but the problem persists on SOAP over JMS Webservices invocations, messages placed on JMS queues (TIBCO EMS queues) which are big and it takes a lot more time than the expected for them to be processed.
7. TIM and SSLv3 Poodle Vulnerability TEC1344045
Description:Recently, RedHat has announced a security vulnerability in SSLv3 protocol, commonly referred to as ‘POODLE’. See the following link for information:
CA has determined TIM Admin UI application (TIM’s webserver) is impacted with this vulnerability. Additionally, communication between the APM CE (CEM) TIM appliance software and the APM Enterprise Manager is affected if SSL communication is enabled between the two components.
8. The RTTM Service will not start. Instead, it appears to be stuck and the Status is "IN PROGRESS". What should I do to get the Service started? TEC596475
Description:The RTTM service in APM can get stuck and display in the APM CEM GUI that the status of the service is "In Progress". This status persists across restarts of the Enterprise Manager, and the Start and Stop buttons are not available to click.
Using a database tool (such as pgadmin III or SQL*Plus), access the APM Database, and open the table "ts_monitor_child_service". Look for the item where the column "ts_child_service_id" is "7", and check the value of the column "ts_started" - it will have a value of "2". If the issue persists, contact CA Technologies APM Technical Support for next steps. This could include an upgrade to a later release where certain causes of this condition have been eliminated.
9. 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 22.214.171.124, by Michal Lehotsky. The original document discusses ways to detect if statistical aggregation is not working and how to correct it. This update adds the following new topics:
•Definition of key terms•Common stats aggregation issues (bad rows, daily aggregation failure, others)•Common defect aggregation issues•Oracle update SQL statements•SQL statements for specific dates•Useful logs•References•Other things to check
10. Getting "Oracle: org.hibernate.exception.GenericJDBCException: Cannot open connection. APM Database is not reachable. Please check the connectivity" message. What can be done to resolve this? TEC596118
Description: Seeing the following messages in the EM (MOM or Tim Collector) logs:
[PO:AppMapAgentPO Mailman 1] [Apm.Data.Model] [ Method : saveAllEdges, RootCause : A ResourcePool could not acquire a resource from its primary factory or source., Error Message : Could not open Hibernate Session for transaction org.hibernate.exception.GenericJDBCException: Cannot open connection]
[ERROR] [WrapperSimpleAppMain] [Apm.Data.Model] APM Database is not reachable. Please check the connectivity…
org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: Cannot open connection; uncategorized SQLException for SQL [???]; SQL state [null]; error code ; Connections could not be acquired from the underlying database!; nested exception is java.sql.SQLException: Connections could not be acquired from the underlying database!
These errors are indicating connection to the APM Database is not available.
11. A simple explanation for "Transaction trace component limit" TEC597762
Description:In an em.log or similar APM log, what does this mean, in simple terms?
[WARN] [IntroscopeAgent.WilyTransactionStructure] Transaction trace component limit of 5000 reached, recording of any new components will cease for this transaction.
12. How do I monitor Adobe Experience Manager using APM Introscope Java Agent ? TEC1750412
Description: How do I monitor Adobe Experience Manager using APM Introscope Java Agent
13. 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 trust the publisher prompt appears. However the Workstation does not start and no error messages are displayed
14. 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.
15. 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.
16. How to set up JBoss 6 EAP with the Introscope Agent and see JMX metrics TEC606597
Description: 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.
17. 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
18. Adding a 9.7 TIM Monitor generates ApmPacketComm errors including "Exiting on timeout reading magic number from apmpacket." TEC1899327
Description: After adding a TIM monitor, a series of error messages appear including:
**ERROR timapmpacketcomm: exiting on timeout reading magic number from apmpacket **ERROR hub: ApmPacketComm: E0Ffrom timapmpacketcomm **ERROR hub: ApmPacketComm: error sending config client request to timapmpacketcomm
19. .NET Agent OOM, High CPU - Checklist TEC596327
Description: .NET Agent OOM, High CPU - Checklist
20. Can SSL packet decode failures be due to TCP false connections? TEC609607
Description: The TIM Settings screen shows a high degree of SSL decode failures. APM is showing defects and statistics. What could be another reason for SSL decode failures?