Direct link to fix
APAR status
Closed as program error.
Error description
When an IBM Business Process Manager (BPM) application server (cluster member) starts, you see the following exception in the SystemOut.log file: [1/18/17 5:33:57:096 EST] 00000070 XARecoveryDat W WTRN0005W: The XAResource for a transaction participant could not be recreated and transaction recovery may not be able to complete properly. The resource was [com.ibm.ws.sib.ra.recovery.impl.SibRaXaResourceInfo@-1915716022 <busName=BPM.De1.Bus> <meName=MECluster.000-BPM.De1.Bus> <meUuid=14AE2851B2F14823> <userName=null> <password=null> <useServerSubject=false> <providerEndpoints=bpm.acme.com:7286:BootstrapSecureMessaging>]. The exception stack trace follows: com.ibm.ws.Transaction.XAResourceNotAvailableException: com.ibm.wsspi.sib.core.exception.SINotAuthorizedException: CWSIT0094E: The client was not authorized to connect to bus BPM.De1.Bus using the bootstrap server with endpoint bpm.acme.com:7286:BootstrapSecureMessaging. Reason: CWSIT0109E: The application did not specify a user ID when attempting authorization with the bus BPM.De1.Bus. at com.ibm.ws.sib.ra.recovery.impl.SibRaXaResourceFactory.getXAReso urce(SibRaXaResourceFactory.java:114) at com.ibm.ws.Transaction.JTA.XARecoveryData.getXARminst(XARecovery Data.java:490) at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData .java:656) at com.ibm.tx.jta.impl.PartnerLogTable.recover(PartnerLogTable.java :432) at com.ibm.tx.jta.impl.RecoveryManager.resync(RecoveryManager.java: 1543) at com.ibm.tx.jta.impl.RecoveryManager.performResync(RecoveryManage r.java:2276) at com.ibm.ws.tx.jta.RecoveryManager.performResync(RecoveryManager. java:119) at com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:222 9) at java.lang.Thread.run(Thread.java:798) Caused by: com.ibm.wsspi.sib.core.exception.SINotAuthorizedException: CWSIT0094E: The client was not authorized to connect to bus BPM.De1.Bus using the bootstrap server with endpoint bpm.acme.com:7286:BootstrapSecureMessaging. Reason: CWSIT0109E: The application did not specify a user ID when attempting authorization with the bus BPM.De1.Bus. at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.generat eException(TrmSICoreConnectionFactoryImpl.java:992) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.contact BootstrapService(TrmSICoreConnectionFactoryImpl.java:715) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.remoteB ootstrap(TrmSICoreConnectionFactoryImpl.java:589) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.connect FromInsideServer(TrmSICoreConnectionFactoryImpl.java:418) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.localBo otstrap(TrmSICoreConnectionFactoryImpl.java:323) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.createC onnection(TrmSICoreConnectionFactoryImpl.java:304) at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.createC onnection(TrmSICoreConnectionFactoryImpl.java:222) at com.ibm.ws.sib.ra.recovery.impl.SibRaXaResourceInfo.createConnec tion(SibRaXaResourceInfo.java:554) at com.ibm.ws.sib.ra.recovery.impl.SibRaXaResourceInfo.createXaReso urce(SibRaXaResourceInfo.java:328) at com.ibm.ws.sib.ra.recovery.impl.SibRaXaResourceFactory.getXAReso urce(SibRaXaResourceFactory.java:103) ... 8 more
Local fix
In the WebSphere administrative console, go to Resources > JMS > Topic connection factories > BPM_BusinessEvents_Topic_CF and note the authentication alias name in the "Authentication alias for XA recovery" field. The default value is DeAdminAlias. Set the same XA recovery authentication alias for all other connection factories that IBM BPM uses, including queue connection factories and topic connection factories.
Problem summary
If the XA recovery authentication alias is not defined in some connection factories that IBM BPM uses, an XA recovery exception might occur when the server starts.
Problem conclusion
A fix will be available in IBM BPM V8.5.7 cumulative fix 2017.06 that sets the XA recovery authentication alias for the connection factories IBM BPM uses. To determine whether the cumulative fix is available, complete the following steps on Fix Central (http://www.ibm.com/support/fixcentral): 1. On the Select product tab, select WebSphere as the product group, IBM Business Process Manager with your edition from the WebSphere options, All as the installed version, and All as the platform, and then click Continue. 2. In the Text field, enter "cumulative fix", and click Continue. If cumulative fix 2017.06 is available, download and install it. 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
Comments
APAR Information
APAR number
JR57497
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-27
Closed date
2017-05-25
Last modified date
2017-05-25
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 STANDARD
Fixed component ID
5725C9500
Applicable component levels
R857 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 May 2017