IBM Support

How to start Business Automation Workflow (BAW) after getting the message CWSIP0291W: An attempt to send a message to exception destination when configure to connect to BAI

How To


Summary

You have a working Business Automation Workflow environment and enabled the Dynamic Event Framework (DEF) to subscribe to IBM Business Automation Workflow events and installed the BPMEventEmitter application to emit BPMN events. You want to connect Business Automation Workflow to BAI and monitor the events. All of the sudden your Business Automation Workflow environment stops working and you see a similar message on the messaging engine logs

CWSIP0291W: An attempt to send a message to <somebusname_> exception destination failed due to the following:
<somebusname_>.Bus is not available because the high limit for the number of messages for this destination has already been reached.

Here is a complete stack for comparison purposes:
8/12/22 11:48:10:108 BRT] 00000127 SibMessage W [:] CWSIP0291W: An attempt to send a message to exception destination _SYSTEM.Exception.Destination.MECluster.000-BPM.WS-busname.Bus on messaging engine MECluster.000-BPM.WS-busname.Bus failed due to the following: com.ibm.ws.sib.processor.exceptions.SIMPLimitExceededException: CWSIK0025E: The destination _SYSTEM.Exception.Destination.MECluster.000-BPM.WS-busname.Bus on messaging engine MECluster.000-BPM.WS-busname.Bus is not available because the high limit for the number of messages for this destination has already been reached.


Objective

Since Business Automation Workflow is used for the work on running processes the goal is to get Business Automation Workflow running again as soon as possible, and then worry about the message and the communication with BAI.

Environment

Business Automation Workflow configured the BPM event emitter to send events from BPMN processes, BPEL processes, and BPEL human tasks or ODM events to a Kafka server.

Steps

  1. Find the defconfig.xml file.
    • The defconfig.xml file holds the DEF configuration and must be present in the IBM Business Automation Workflow Deployment Manager profile at this location: <BAW_Install_Root>/profiles/DmgrProfile/config/cells/<CellName>.
  2. Change defconfig.xml to whatever.xml
    • Essentially you disable the emissions of events altogether, no more events are emitted to the queue.
  3. Do a full resynchronize in WebSphere Application Server including the dmgr and node levels. Do a full restart.
    • Verify the defconfig.xml file does not exist anywhere on the system, check the dmgr and the nodes, and if the file still exists remove the file and repeat step 3.
Afterward the Business Automation Workflow is up and running, you would then most likely want to speak with support to help figure out why BAW/ODM is not communicating with BAI. 

Additional Information

Here are a few related articles to BAI communication configuration and troubleshooting for BPM:

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"ARM Category":[{"code":"a8m0z000000XauvAAC","label":"Workflow Monitoring-\u003EBAI BPM Event Emitter"}],"ARM Case Number":"TS010271154","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Product Synonym

BAW; BAI; DEF

Document Information

Modified date:
30 March 2023

UID

ibm16963394

Page Feedback