In BusinessWorks, the BusinessConnect event starter (Receive Request) will not confirm messages from JMS.
Article ID: KB0084398
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| TIBCO BusinessConnect Palette | - |
Description
When inbound messages are received from the EMS/JMS queue to the BusinessWorks BusinessConnect Process Starter (either Receive Request or Receive Response), it appears that these requests from BC are looping infinitely. The process is triggered with the same message multiple times even if previous invocation completed "Confirm" activity without errors.
Symptoms:
If you enable the bc.palette.tracing global variable in the BW project, this type of message is observed in the audit log:
2016 Jan 27 14:59:59:072 CET => BC Palette [DEBUG]: Message dispatched successfully with id '162729232'.
2016 Jan 27 14:59:59:116 CET => BC Palette [DEBUG]: Custom-confirming message with id '162729232'.
2016 Jan 27 14:59:59:151 CET => BC Palette [DEBUG]: JMS Consumer is closing on: [QUEUE] Roche.Pharma.Lifecycle.OP.BC-Lifecycle.RESPONDER.REQUEST
.
.
2016 Jan 27 14:59:59:155 CET => BC Palette [DEBUG]: JMS Consumer started on: [QUEUE] AX.BC.<BC_instance_name>.RESPONDER.REQUEST
2016 Jan 27 14:59:59:155 CET => BC Palette [DEBUG]: JMS transport has successfully restarted for task 'ReceiveRequest'.
Cause:
FlowLimit parameter on process starter set too close to MaxJobs parameter to control sequencing of inbound jobs from BusinessConnect.
Issue/Introduction
Resolution
FlowLimit.ReceiveRequest.process=1
MaxJobs.ReceiveRequest.process=1
The FlowLimit parameter should be set to at least twice the MaxJobs parameter. When the Flow Limit is reached, part of the BW BC palette shuts down, which can causes messages to go into a continuous loop because they are never fully processed.
Feedback
