Sometimes an application creates multiple connection pools that all point to the same database which means that the transaction recovery system will invoke the XA recover () call multiple times for the same list of transaction branches that are currently in a prepared or heuristically completed state. For performance reasons it would be nice if only one of them could be marked as eligible for recover calls.

There is a precedent for this feature in the WildFly datasource subsystem model.