Connection handle to database remains active indefinitely #32789
Description
Describe the bug
When a transaction times out and is rolled back, connection handles remain active indefinitely in the connection pool. This occurs because when MCWrapper.incrementHandleCount() is called during connection allocation, there's no corresponding MCWrapper.decrementHandleCount() call if the operation fails with a ResourceException. This leads to connection pool exhaustion as handles remain at a count of 1 instead of returning to 0.
Expected behavior
When a transaction times out and is rolled back, all connection handles should be properly decremented and returned to the pool, maintaining the health of the connection pool even under error conditions.
This issue is tracked under APAR PH68082