Improvement #2159
Updated by Henning Blohm 20 days ago
In case of connection leaking, it is rather hard to find that a) some thread is waiting for a connection and b) who is leaking. h2. Acceptance Criteria * When waiting longer than 10s for a connection, log a warning. * Repeat the warning with counts after some delay if necessary a call stack * Provide JMX statistics For JTA enlisted connections that are not used in a JTA context, warn and enlist to close and rollback in the workunit anyway.