First of all - you should use WildFly 8 Alpha1
And, precisely the database you are using is the reason the check is in place. It changes the passed in properties object.
However, you havn't posted your configuration nor profiling data, so maybe you aren't using an optimal configuration for your case. Lets see it.
And, we welcome any patches that improves this scenario.
Isn't the matching only useful in scenarios where the same pool stores 'different' DB connections (differnet username/pswd) ?
I suspect that jboss 7 'blocks' (in synchronised calls) a lot more than jboss 5 did during pooling. The 'matchManagedConnections' is one occurence. Another one is org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool#getConnection.
Anyway, i'll try do some more testing/measuring tomorrow.
Not if the database changes the objects we pass in...
The JDBC resource adapter is almost the same as was included in 3/4/5/6.
Yeah, do that...