iProcess Engine BG process blocked running EAI_BW steps - message queues building, nothing being processed
Article ID: KB0076303
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | All Supported Versions |
Description
TIBCO iProcess Engine BG process blocked running EAI_BW steps - message queues building, nothing being processed.
EAIJAVA debug was enabled to capture more detailed information.
The eaijava debug logs indicate that the BG processes are hung executing an Immediate release EAI_BW step. Issue affected one Immediate release EAI_BW step in a procedure.
The last entries in the eaijava log is:
2020-01-21 10:27:55,981 [DEBUG] SWBWTransport - Waiting for JMS response (Response Timeout Period:120000)
2020-01-21 10:29:55,981 [WARN ] SWBWTransport - JMS response timed out after 120000 milliseconds (Response Timeout Period)
2020-01-21 10:29:55,982 [INFO ] SWBWTransport - Attempting to re-consume message with ID: ID:EMS-SERVER.5DFF5DF66578C917:3
No further processing after the plug-in attempts to re-consume the message from the EMS queue.
The BG processes were blocked and unresponsive to being stopped using the iProcess swsvrmgr and swstop commands.
EAIJAVA debug was enabled to capture more detailed information.
The eaijava debug logs indicate that the BG processes are hung executing an Immediate release EAI_BW step. Issue affected one Immediate release EAI_BW step in a procedure.
The last entries in the eaijava log is:
2020-01-21 10:27:55,981 [DEBUG] SWBWTransport - Waiting for JMS response (Response Timeout Period:120000)
2020-01-21 10:29:55,981 [WARN ] SWBWTransport - JMS response timed out after 120000 milliseconds (Response Timeout Period)
2020-01-21 10:29:55,982 [INFO ] SWBWTransport - Attempting to re-consume message with ID: ID:EMS-SERVER.5DFF5DF66578C917:3
No further processing after the plug-in attempts to re-consume the message from the EMS queue.
The BG processes were blocked and unresponsive to being stopped using the iProcess swsvrmgr and swstop commands.
Issue/Introduction
TIBCO iProcess Engine BG process blocked running EAI_BW steps - message queues building, nothing being processed
Environment
TIBCO iProcess Technology Plug-ins all versions, database types and platforms
Resolution
Custom timeout values can be specified in an EAI_BW step.
Custom timeout values override the default timeout values.
The default timeout values are configured on the iProcess server in the file SWDIR/eaijava/properties/bw/jms.properties
The affected EAI_BW step was configured with the following custom timeout values:
Response Timeout 120000
Consume Timeout 0
Deadlock Timeout 0
Expiration Timeout 140000
A timeout value of 0 means no timeout.
There is a reference to specifying 0 for a timeout in the TIBCO iProcess BusinessWorks Connector User’s Guide, section The Configure Message Timeouts Dialog:
https://docs.tibco.com/pub/ip-tech-pi/11.7.0/doc/html/wwhelp/wwhimpl/js/html/wwhelp.htm#href=TIB_ip-tech-pi_users_guide/eai_bw.09.5.htm#1812402
The plug-in is hung until the message is re-consumed from the EMS queue. The message could not be re-consumed because the message had been read by BusinessWorks.
Eventually, all BG processes were hung with this issue.
The resolution is to update the EAI_BW steps and configure the custom timeout values to be non-zero.
For example:
Response Timeout 120000
Consume Timeout 5000
Deadlock Timeout 240000
Expiration Timeout 140000
After updating the EAI_BW step definition:
1. Release the new procedure version
2. Migrate cases of the previous procedure version to the new version
3. Kill the blocked BG processes to enable the process to be restarted
Custom timeout values override the default timeout values.
The default timeout values are configured on the iProcess server in the file SWDIR/eaijava/properties/bw/jms.properties
The affected EAI_BW step was configured with the following custom timeout values:
Response Timeout 120000
Consume Timeout 0
Deadlock Timeout 0
Expiration Timeout 140000
A timeout value of 0 means no timeout.
There is a reference to specifying 0 for a timeout in the TIBCO iProcess BusinessWorks Connector User’s Guide, section The Configure Message Timeouts Dialog:
https://docs.tibco.com/pub/ip-tech-pi/11.7.0/doc/html/wwhelp/wwhimpl/js/html/wwhelp.htm#href=TIB_ip-tech-pi_users_guide/eai_bw.09.5.htm#1812402
The plug-in is hung until the message is re-consumed from the EMS queue. The message could not be re-consumed because the message had been read by BusinessWorks.
Eventually, all BG processes were hung with this issue.
The resolution is to update the EAI_BW steps and configure the custom timeout values to be non-zero.
For example:
Response Timeout 120000
Consume Timeout 5000
Deadlock Timeout 240000
Expiration Timeout 140000
After updating the EAI_BW step definition:
1. Release the new procedure version
2. Migrate cases of the previous procedure version to the new version
3. Kill the blocked BG processes to enable the process to be restarted
Feedback
Yes
No
Powered by
