-
1. Re: Error in use of ManagedConnectionPool
begram Mar 6, 2003 6:25 AM (in response to hounce)I got the same behaviour with my connector in JBOSS 3.0.6 with Tomcat.
The error occur when the matchManagedConnections in the ManagedConnectionFactory return null.
If I understand the documentation right, the ManagedConnectionFactory implementation shall decide if there is a matching connection, NOT the application server. Is this a bug in JBOSS? -
2. Re: Error in use of ManagedConnectionPool
begram Mar 6, 2003 6:28 AM (in response to hounce)I got the same behaviour with my connector in JBOSS 3.0.6 with Tomcat.
The error occur when the matchManagedConnections in the ManagedConnectionFactory return null.
If I understand the documentation right, the ManagedConnectionFactory implementation shall decide if there is a matching connection, NOT the application server. Is this a bug in JBOSS? -
3. Re: Error in use of ManagedConnectionPool
begram Mar 6, 2003 6:30 AM (in response to hounce)I got the same behaviour with my connector in JBOSS 3.0.6 with Tomcat.
The error occur when the matchManagedConnections in the ManagedConnectionFactory return null.
If I understand the documentation right, the ManagedConnectionFactory implementation shall decide if there is a matching connection, NOT the application server. Is this a bug in JBOSS? -
4. Re: Error in use of ManagedConnectionPool
davidjencks Mar 7, 2003 10:51 PM (in response to hounce)The current pool implementation assumes that it can predict what will and won't match. It can use the Subject alone, ConnectionRequestInfo alone, both, or none. You set what it will use with the criteria attribute of the pool
IMO this gives us the best concurrency in the connection manager, and so far it hasn't been a real problem. I need to see a reasonable example of an adapter that distinguishes connections for matching on some basis other that the cri and subject before I will consider writing an additional pool implementation for this case. Remember that the cri class is required to implement hashcode and equals based on all the properties the MCF can use for matching.