Non spec compliant behavior of matchManagedConnections

SourceForge Submitter: janssk1 .
the current (3.2.1 and CVS) implementation of
InternalManagedConnectionPool does not match the JCA
specification 1.0. The Spec. specifies that : "If the
application server finds no matching ManagedConnection
instance that can best handle this connection request,
or if the candidate set is empty, the application server
calls the
ManagedConnectionFactory.createManagedConnection
method."

In the implementation of JBoss the behaviour is
different. If the matchManagedConnection returns null
(no match found) the implementation will destroy the
managed connection.

This is probably related to the comment made in the
code:
"
//Match did not succeed but no exception was thrown.
//Either we have the matching strategy wrong or the
//connection died while being checked. We need to
//distinguish these cases, but for now we always
//destroy the connection.
"

In our case the matchManagedConnection is rather
important because one managed connection cannot be
replaced by another one.