APAR status
Closed as program error.
Error description
The following entry is showing up in the EKM Audit Log. This entry with outcome= result=successful but the message resource= name=Process Message failed; posses an inherent level of confusion for the customer. Having a failed message with result successful is quite confusing. Runtime event: timestamp=Thu Dec 11 08:28:00 EST 2008 ComponentId= threadId=Thread Thread-186,5,KeyManagementServerV2-Processo rs rs event source=com.ibm.keymanager.logic.Logic outcome= result=successful event type=SECURITY_RUNTIME resource= name=Process Message failed;type=file action=start The "Process Message failed" message appears in the Audit log exactly 30 minutes after successfully reading or writing a tape. This time is based on the TransportListener.tcp.timeout property. For example if the TransportListener.tcp.timeout = 30 in the properties file. This means that when there is no longer any communication on the socket for 30 minutes, EKM will close the socket. While this is a benign effect on the program, the Process Message failed implies something is wrong and should be clearer or documented so customers are aware of the messages meaning.
Local fix
Problem summary
The following entry is showing up in the EKM Audit Log. This entry with outcome= result=successful but the message resource= name=Process Message failed; posses an inherent level of confusion for the customer. Having a failed message with result successful is quite confusing. Runtime event: timestamp=Thu Dec 11 08:28:00 EST 2008 ComponentId= threadId=Thread Thread-186,5,KeyManagementServerV2-Processors event source=com.ibm.keymanager.logic.Logic outcome= result=successful event type=SECURITY_RUNTIME resource= name=Process Message failed;type=file action=start The "Process Message failed" message appears in the Audit log exactly 30 minutes after successfully reading or writing a tape. This time is based on the TransportListener.tcp.timeout property. For example if the TransportListener.tcp.timeout = 30 in the properties file. This means that when there is no longer any communication on the socket for 30 minutes, EKM will close the socket. While this is a benign effect on the program, the Process Message failed implies something is wrong and should be clearer or documented so customers are aware of the messages meaning.
Problem conclusion
The message in the EKM Audit Log has been modified to Process Message: TransportListener socket timed out...closing socket. Runtime event:[ timestamp=Thu Mar 26 21:17:37 CDT 2009 ComponentId=[threadId=Thread[Thread-715,5,KeyManagementServerV2- Processors]] event source=com.ibm.keymanager.logic.Logic outcome=[result=successful] event type=SECURITY_RUNTIME resource=[name=Process Message: TransportListener socket timed out...closing socket;type=file] action=start ] IBMKeyManagementServer.jar dated 20090325 - JVM 1.4.2 sr14 IBMKeyManagementServer.jar dated 20090325 - JVM 1.5.0 sr10 IBMKeyManagementServer.jar dated 20090325 - JVM 1.6.0 sr5 Hursley Defect 148532
Temporary fix
Comments
APAR Information
APAR number
IZ42448
Reported component name
TIV TAPE ENCRY
Reported component ID
TIVOEKM00
Reported release
121
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-23
Closed date
2009-03-30
Last modified date
2009-03-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TIV TAPE ENCRY
Fixed component ID
TIVOEKM00
Applicable component levels
R100 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC6LF3","label":"EKM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"121","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 March 2009