I need to see the logs to get more details , enable the log tracing for
org.jboss.resource.connectionmanager.JBossManagedConnectionPool and attach it
here .
try
| {
| Object matchedMC =
mcf.matchManagedConnections(Collections.singleton(cl.getManagedConnection()),
| subject, cri);
| if (matchedMC != null)
| {
| if (trace)
| log.trace("supplying ManagedConnection from
pool: " + cl);
| cl.grantPermit(true);
| return cl;
| }
|
| //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.
| log.warn("Destroying connection that could not be
successfully matched: " + cl);
| synchronized (cls)
| {
| checkedOut.remove(cl);
| }
The above code is from
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/connector/src/main/org/jboss/resource/connectionmanager/InternalManagedConnectionPool.java
It is this code which is displaying the warning .
Looks to me the issue with matchManagedConnection implementation of MCF .
Give me more details about the MCF implementation of matchManagedConnection .
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116348#4116348
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116348
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
