Enhancement Request – Socket Timeout Property for MQ Adapter

Currently, in the MQ Adapter, we only have Block Timeout (msec) and Expire Timeout (msec) properties to manage connection timeouts. However, these settings do not effectively handle scenarios where a thread is waiting indefinitely for a response from the end system.

Unlike the JDBC Adapter, which provides the socketTimeout=y property to control the maximum amount of time a thread waits for a response from the database, the MQ Adapter lacks a similar property to manage socket-level timeouts. The absence of this feature can lead to prolonged or stuck threads when the end system does not respond in a timely manner, potentially affecting system performance and resource utilization.

Proposed Enhancement:

We propose introducing a Socket Timeout property at the connection level for the MQ Adapter, similar to the socketTimeout property in the JDBC Adapter.

• Expected Behavior:
  • The new property should define the maximum duration (in milliseconds) that a socket operation can wait before timing out.

We request that this enhancement be reviewed by the R&D team and included in a future release or patch for the MQ Adapter. Additionally, if there are any existing workarounds or alternative configurations to address this issue in the current setup, please advise.

We appreciate your support in evaluating this request and look forward to your feedback on feasibility and potential timelines.