If you have setup a traditional BAW environment with external CPE and ICN (using a template from ../BPM/samples/config/externalicnexternalcpe) or upgraded an existing Case Manager installation to BAW, you may encounter javax.transaction.HeuristicMixedException exception while creating a case, updating security of a project area or any other operation that involves all three components i.e. BAW, CPE and ICN.
[Image 1: Error during case creation]
[Image 2: Error during Project Area security update]
Exception during case creation ( ICN -> SystemOut.log):
com.ibm.ecm.extension.icm.services.impl.CaseService.execute()
com.filenet.api.exception.EngineRuntimeException: FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred. Message was: ; nested exception is: javax.transaction.HeuristicMixedException errorStack={
at com.filenet.engine.ejb.EJBUtil.determineException(EJBUtil.java:91)
at com.filenet.engine.ejb.EngineBean.executeChanges(EngineBean.java:972)
at com.filenet.apiimpl.transport.ejbstubs.EJSRemoteStatelessEngine_2e64c374.executeChanges(EJSRemoteStatelessEngine_2e64c374.java)
Exception during adding users to a Project Area (ICN -> SystemOut.log):
[1/4/22 8:01:34:667 IST] 000000df SystemOut O CIWEB.ICMAdminClientPlugin Error: [xxxxx @ xxx.xxx.xxx.xxx] com.ibm.ecm.icm.accm.repository.ManageProjectArea.addUsersToProjectArea()
com.filenet.api.exception.EngineRuntimeException: FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred. Message was: ; nested exception is: javax.transaction.HeuristicMixedException errorStack={
at com.filenet.engine.ejb.EJBUtil.determineException(EJBUtil.java:91)
at com.filenet.engine.ejb.EngineBean.executeChanges(EngineBean.java:972)
at com.filenet.apiimpl.transport.ejbstubs.EJSRemoteStatelessEngine_2e64c374.executeChanges(EJSRemoteStatelessEngine_2e64c374.java)
This happens due to a mismatch in the settings of WS-Transaction specification level and Enable transaction coordination authorization flag on BAW, CPE and ICN application servers.
By default, tWAS profiles are created with the following settings (Application servers > server1 > Transaction service):
- "Enable Transaction Coordination authorization" is checked (True)
- "WS-Transaction" to
1.0
[Image 3: Default Transaction service settings]
However, the Deploy the Content Platform Engine Gateway Service (i.e. deploygateway) task, which is a mandatory task for Case component of BAW, changes the values on CPE application server(s) to:
- "Enable Transaction Coordination authorization" is unchecked (False)
- "WS-Transaction" to 1.1
[Image 4: Updated settings post deploygateway task execution]
This difference in the configuration leads to HeuristicMixedException and makes the Case part of the BAW unusable. You must change the settings on CPE application server(s) back to the default setting manually to fix this issue. This applies to all versions of BAW including the recent release 21.0.3. Future releases of BAW may include a fix for this issue.