BusinessConnect stops working suddenly while performing transactions using EDI protocol

BusinessConnect stops working suddenly while performing transactions using EDI protocol

book

Article ID: KB0073438

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream 6.9.0 and later

Description

While performing EDI transactions, the BusinessConnect Interior Server (IS) stops processing files without any indications of network issues or any noticeable errors in the IS logs. This generally happens because there are a crash in the Instream Translator inside the BusinessConnect engine
While using EDI protocol, a translator is invoked when IS needs to convert an XML request to the standard EDI format (outbound transaction) or an EDI document to an XML request (inbound transaction). In both scenarios, the translator is expected to handle the conversion task in sequential order. However, under a heavy load of transactions, this task might fail.

Environment

All platforms

Resolution

- To handle this, add a property named - 'edi.translator.forceThreadLocking' in the Admin GUI under the following path - (BusinessConnect > System Settings > Activated Protocol Plug-ins and Properties > tibEDI).

- After adding this boolean property in the specified path, there will be a checkbox in front of it which needs to be enabled. This indicates the property is now set to 'true' and the thread-locking is enabled. This will  help the translator handle the conversion task in a sequential manner.  This property will not impact BC performance.

- Once the above steps are implemented, please restart the IS engine/s.

You may also refer to the attached screenshot:  EDI_threadlocking.png
 
Note: Please implement the suggested changes during system downtime.

Issue/Introduction

BusinessConnect stops working suddenly while performing transactions using EDI protocol

Attachments

BusinessConnect stops working suddenly while performing transactions using EDI protocol get_app