Dmitri Voronov [http://community.jboss.org/people/dimonv] created the discussion "Re: re-authentication and pooling" To view the discussion, visit: http://community.jboss.org/message/592610#592610 -------------------------------------------------------------- You wrote in your article: None of the options provide a solution for the issue described in the original post: * the fact that a JCA resource adaptor may support multiple types of the underlying connections. That means - pooling by CRI at least. * pooling by Subject (I pressume you mean it with credantials) may cause too many sub-pools in case of a big numgber of users. The consequence is that max pool size = max pool size x number of users. In my opinion the pooling should depend on the re-authentication capability of adapter. If an adapter declares that it supports re-authentication - pool by CRI, if not - pool by Subject and CRI. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/592610#592610] Start a new discussion in IronJacamar at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dmitri Voronov [http://community.jboss.org/people/dimonv] created the discussion "Re: re-authentication and pooling" To view the discussion, visit: http://community.jboss.org/message/592814#592814 -------------------------------------------------------------- Sorry, but this topic is about two years old and refers to the code base from AS 4.2.3.GA and I was trying to find a solution for a real issue, which has never been commented here. I spent about an year on discussing it in EAP support portal and then was invited to discuss in the community.  Can you explain please what is wrong. What do you mean with: You are using a reference to it in JIRA and in your article. In the previous message I commented the article's chapter "Design" and not the implementation in IronJacamar. I looked at ReauthKey in the trunk. It does't even use CRI neither in its equals() method not elsewhere. I wrote: I meant several Java types e.g. EJB business interfaces, File/Path, Http/Https-Connections any specific classes from a hierarchy etc.. And this information may be a part of CRI. And if a requested connection should support e.g. HTTPS but if a connection obtained from the pool is an insecure one it is wrong. Read section 6.5.1.2. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/592814#592814] Start a new discussion in IronJacamar at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]