Socket Exception occurs during Orphan Management execution - ConnectALL
search cancel

Socket Exception occurs during Orphan Management execution - ConnectALL

book

Article ID: 441913

calendar_today

Updated On:

Products

ConnectAll On-Prem ConnectALL

Issue/Introduction

You encounter a java.net.SocketTimeoutException: Read timed out or Socket Exception when running Orphan Management (OM) in ConnectALL. This issue specifically appears when a Jira issue undergoes a change that triggers OM (such as changing an issue type from Epic to Story, or deleting its pair from the alternate system), but the original item is not picked up or processed.

Symptoms

  • Orphan Management logs contain jakarta.ws.rs.ProcessingException: java.net.SocketTimeoutException: Read timed out.
  • The error occurs consistently for items with long history logs.
  • Manual runs or scenarios with shorter history logs (e.g., Story to Epic) may work as expected.
  • You see log entries similar to: ERROR #### [#### | #### | ## | ##### | {new_group}][(orphan-flows) thread ### - JmsConsumer[findOrphanQ]] com.go2group.connectall.jira.JiraRestConnector: Exception in getting modified records.

Environment

ConnectALL versions below 4.2

Cause

This issue occurs because Orphan Management requests the full Jira history when the "Jira Sync with Changelog" option is enabled in the automation's Entity Mappings. For Jira items with an extensive history, the data retrieval process exceeds the hardcoded two-minute (120-second) read timeout period in the Jira adapter.

Resolution

Fixed in release v4.2 and higher. See  for steps to download this release.

Workaround

If you cannot immediately upgrade to v4.2, use the following steps to mitigate the timeout:

  1. Navigate to the Entity Mapping tab for the affected automation.
  2. Locate the Flow Properties.
  3. Disable the "Jira Sync with Changelog" option.
  4. Reschedule or re-run the Orphan Management process.

Note: Disabling the changelog prevents Orphan Management from requesting the extensive history logs that trigger the timeout but may also impact some product functionality such as moving issues between projects.