Direct links to fixes
APAR status
Closed as program error.
Error description
The following warning message occurs in the SystemOut.log file after getFailedEventCount() is invoked repeatedly: [6/24/14 13:59:01:914 CEST] 00000065 Recovery W com.ibm.wbiserver.manualrecovery.ext.util.BPCExtensionUtil getFailedEventCountInTarget() CWRCV0096W: An exception occurred while getting the failed event count from business process container with JNDI name cell/clusters/esbOCluster/com/ibm/bpe/api/ BusinessFlowManagerHome. Error java.rmi.AccessException: CORBA NO_PERMISSION 0x49421096 No; nested exception is: org.omg.CORBA.NO_PERMISSION: SERVER (id=1f77a32e, host=xxx) TRACE START: org.omg.CORBA.NO_PERMISSION: Null TokenHolder list returned from authorization token. vmcid: 0x49421000 minor code: 96 completed: No at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRIBase. handlePropagationToken(CSIServerRIBase.java:923) at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRI. receive_request(CSIServerRI.java:551) at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor (InterceptorManager.java:624) at com.ibm.rmi.pi.InterceptorManager. iterateServerInterceptors(InterceptorManager.java:528) at com.ibm.rmi.pi.InterceptorManager. iterateReceiveRequest(InterceptorManager.java:770) at com.ibm.CORBA.iiop.ServerDelegate. dispatchInvokeHandler(ServerDelegate.java:667) at com.ibm.CORBA.iiop.ServerDelegate.dispatch (ServerDelegate.java:525) at com.ibm.rmi.iiop.ORB.process(ORB.java:576) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1578) at com.ibm.rmi.iiop.Connection.doRequestWork (Connection.java:3076) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2946) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:64) There is no functional impact to the caller of the method. This APAR moves the warning-type message out of the SystemOut.log file and into the Business Process Choreographer trace. This results in a clean log and the information is available if any problems need to be analyzed.
Local fix
Problem summary
A warning message with no functional impact to the caller of the method is written to the SystemOut.log frequently.
Problem conclusion
A fix is available for IBM BPM V8.0.1.3 that turns the warning message into a trace message to avoid filling the log file yet preserve the message in case it is needed for debugging. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR51152: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR51152, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Not applicable
Comments
APAR Information
APAR number
JR51152
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-09-01
Closed date
2014-11-05
Last modified date
2014-11-05
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R801 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021