Readmes are available
8.1.4.0-IBM-APM-SERVER-IF0001
8.1.4.0-IBM-APM-SERVER-IF0002
8.1.3.0-IBM-IPM-SERVER-IF0011
8.1.4.0-IBM-APM-SERVER-IF0003
8.1.4.0-IBM-APM-SERVER-IF0004
8.1.3.0-IBM-IPM-SERVER-IF0012
8.1.4.0-IBM-APM-SERVER-IF0005
8.1.4.0-IBM-APM-SERVER-IF0006
8.1.3.0-IBM-IPM-SERVER-IF0013
8.1.4.0-IBM-APM-SERVER-IF0007
8.1.3.0-IBM-IPM-SERVER-IF0014
APAR status
Closed as fixed if next.
Error description
Environment: APM Server APM version: 8.1.3 Problem Description: Server1 was encountered a the following problem with the shared class cache: "JVMSHRC340E Shared Cache CRC check failed." which hard stopped the process and caused the RBAC Policy DB to be corrupted. Subsequent starting of the server1 server found all of the previously defined user authorization policies to be corrupted. This APAR fix will disable the usage of the JVM Shared Class Cache for the APM Servers since it was found to have negliable impact to the server's performance. Detailed Recreation Procedure: Cache corruption is not easily recreatable since it depends on failed disk reads. The cache file can be corrupted using an editor. It's found at <install-dir>/wlp/usr/servers/.classCache and is has "_liberty-root_" in it;s name. Related Files and Output: JVM core files, apm-verbose.log, /var/log/messages. jvm.options Messages found in logs etc /tmp/apm-verbose.log and /var/log/message files will both show messages similar to: JVMSHRC340E Shared Cache CRC check failed. Stored CRC bad6bc6, calculated CRC d643a97b JVMSHRC443E Cache CRC is incorrect indicating a corrupt cache. Incorrect cache CRC: 0xd643a97b. JVMDUMP039I Processing dump event "corruptcache", detail "" at 2017/07/26 19:24:52 - please wait. JVMDUMP032I JVM requested System dump using '/opt/IBM/wlp/usr/servers/server1/core javavcore file will also be found in the <install-dir>/wlp/usr/server/? for the affected server.
Local fix
Add the "-Xshareclasses:none" option to the <install-dir>/wlp/usr/server/server1/jvm.options file to eliminate the usage of the shared class cache for this server. APM servers with 8.1.3 IF005 or later installed can may recover the policies when server1 starts, otherwise the policies can be restored from the latest backup. APM server versions prior will need to redefine the lost policy data.
Problem summary
The APAR fix is available in the 8.1.4.0-IBM-APM-SERVER-IF0003 interim fix. See this link for details: http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400003715 The APAR fix is also available in the 8.1.3.0-IBM-IPM-SERVER-IF0011 interim fix. See this link for details: http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400003678
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IV98544
Reported component name
MONITORING INFA
Reported component ID
5725U05IN
Reported release
813
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-31
Closed date
2018-02-14
Last modified date
2018-02-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R813 PSY
UP
R814 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"813","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 February 2018