You experience intermittent timeouts during syncs in your ConnectALL environment. The logs contain the following retriable exception:
com.go2group.connectall.model.transformer.exception.RetriableException: java.util.NoSuchElementException: Timeout waiting for idle object, borrowMaxWaitMillis=####
ConnectALL 4.2
This issue occurs when the target application environment responds slower than expected. The default connection pool settings are too aggressive for the environment's response time, causing the application to time out while waiting for a connection to become available.
You resolve this issue by adjusting the connection pool parameters in the ConnectALL Properties to allow for more concurrent activity and longer wait times.
Follow these steps to update your configuration:
jira.minIdle = 15jira.maxWait = 2000jira.maxActive = 50You do not need to restart the ConnectALL Core service, as it periodically refreshes these settings from the database.
In some cases it may be necessary to increase the values beyond what is shown above. In doing so, increase the values incrementally to prevent unnecessary resource consumption.