I'm interesting on re-authentication as well, but my case relates to a non-JDBC RA (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155124).
Nevertheless I had a look into the patch suggested by Vicky and have some comments regarding org.jboss.resource.connectionmanager.JBossManagedConnectionPool. Even if an RA supports re-authentication, its connections may not be put into a OnePool per default, since their CRIs e.g. types can differ. Moreover if an RA supports re-authentication, it doesn't mean automatically that re-authentication should be applied, I think it's the matter of -ds.xml. The criteria like "ByContainerAndApplication", "ByContainer", which require authentication, do not express any requirements for re-authentication. Probably an addition tag within -ds.xml combined with "ByContainer..." is needed to give org.jboss.resource.connectionmanager.JBossManagedConnectionPool a hint which pool implementation should be used. Thanks and kind regards, Dmitri View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242236#4242236 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242236 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
