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.
jakarta.ws.rs.ProcessingException: java.net.SocketTimeoutException: Read timed out.ERROR #### [#### | #### | ## | ##### | {new_group}][(orphan-flows) thread ### - JmsConsumer[findOrphanQ]] com.go2group.connectall.jira.JiraRestConnector: Exception in getting modified records.ConnectALL versions below 4.2
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.
Fixed in release v4.2 and higher. See for steps to download this release.
If you cannot immediately upgrade to v4.2, use the following steps to mitigate the timeout:
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.