Issue with communication between iProcess and BusinessWorks

2020-01-18 15:30:55,270 [WARN ] SWBWTransport - JMS response timed out after 20000 milliseconds (Response Timeout Period)
2020-01-18 15:31:00,271 [WARN ] SWBWTransport - Failed to re-consume original sent message
2020-01-18 15:35:00,271 [WARN ] SWBWTransport - JMS receive timed out after 240000 milliseconds (Deadlock Timeout Period)
2020-01-18 15:35:00,271 [ERROR] SWBWTransport - BusinessWorks failed to respond in a timely fashion - request withdrawn
2020-01-18 15:35:00,271 [ERROR] SWBWTransport - Unable to send/receive JMS message
javax.jms.JMSException: BusinessWorks failed to respond in a timely fashion - request withdrawn

TIBCO iProcess Engine - all versions, database types and platforms TIBCO iProcess Technology Plug-ins - all versions, database types and platforms

iProcess is sending the message over EMS, however, no response is received from BusinessWorks within the timeout values.

The message is not left on the EMS queue – iProcess is unable to re-consume the message.

The issue is either:

1. The message has been read by BusinessWorks and there is an issue with the BusinessWorks process

or

2. The EMS message has expired on the queue and not read by BusinessWorks– this can only happen if iProcess, BW and EMS run on different servers that are not time synchronized.


Check the logs for the deployed application in BusinessWorks – there may be a delay or error in the BusinessWorks processes.

Issue with communication between iProcess and BusinessWorks