Are you sure? What's supposed to happen is that the ManagedConnection is
only put back into the pool after the transaction it is enrolled in
commits, and requests for a managed connection within the same transaction
use the (single) ManagedConnection already attached to that transaction.
There's a map of transactions to ManagedConnections in the
LocalTxConnectionManager: the ManagedConnection should be there until its
tx commits. Please let me know if this is not happening. Also please
always mention the jboss version you are using.
thanks
david jencks
On 2002.07.31 06:52:08 -0400 "Wink, Stephen" wrote:
> I'm writing a JCA adapter that uses LocalTxConnectionManager. When the
> user calls close() on my connection object, I send a connectionClosed
> event to the listeners on my ManagedConnection, and this causes the
> connection to be returned to the connection pool. However, it seems
> that JBoss won't check the same connection out of the pool again until
> the connection's transaction has been committed or rolled back. Is this
> in fact what JBoss is doing? If not, I'll put some code in my
> implementation of ManagedConnectionFactory.matchManagedConnections(), so
> that a connection that's already in a transaction can't be checked out
> of the pool. Can you tell me whether the LocalTxConnectionManager does
> check whether a connection is in a transaction before making it
> available to be used?
>
> Steve
>
>
> ---
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
