Bugs item #773074, was opened at 2003-07-17 17:47 Message generated for change (Comment added) made by janssk1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=773074&group_id=22866
Category: JBossCX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: gui (janssk1) Assigned to: David Jencks (d_jencks) Summary: Non spec compliant behavior of matchManagedConnections Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: gui (janssk1) Date: 2003-07-18 09:47 Message: Logged In: YES user_id=769377 In our case, only connectionrequest info is used for matching. The problem is that jboss is to eager to destroy non matched connections. It might well be that a connection that does not match for one request *does* match for another one. So instead of always dropping the non matched connection, it might be wiser to keep it, unless the pool is full or something. KR, Koen. ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2003-07-17 18:45 Message: Logged In: YES user_id=60525 Can you please explain the criteria you need to use for matching ManagedConnections? For most adapters, the combination of Subject and ConnectionRequestInfo has been sufficient to ensure correct matching. I think there may be some circumstances where this is not sufficient but I'd like more information before writing another pooling implementation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=773074&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
