Disable the connection tracking feature (disableConnectionTracking = true) as workaround.
Looks like the finalizeReferent method from ConnectionPartition.trackConnectionFinalizer() kicks in when it is not supposed to. I see this method killing off connections that are in use (worker thread: getConnection, Thread.sleep(), closeConnection; while the thread sleeps for a few millis the finalizeReferent can close the connection). Of course it only happens 'sometimes' (must be some sort of concurrency issue/race condition/gc issue with the ReferenceQueue), so it is a pain to debug.
Disable the connection tracking feature (disableConnect ionTracking = true) as workaround.
Looks like the finalizeReferent method from ConnectionParti tion.trackConne ctionFinalizer( ) kicks in when it is not supposed to. I see this method killing off connections that are in use (worker thread: getConnection, Thread.sleep(), closeConnection; while the thread sleeps for a few millis the finalizeReferent can close the connection). Of course it only happens 'sometimes' (must be some sort of concurrency issue/race condition/gc issue with the ReferenceQueue), so it is a pain to debug.