Subject | Pool doesn't reset TransactionIsolation |
---|---|
Author | Rick DeBay |
Post date | 2004-07-22T22:51:51Z |
Jaybird RC3, JBoss 3.2.5, firebirdsql.rar drivers.
If I request connections from the pool and set their isolation level to
greater than READ_COMMITTED, after returning them to the pool I am later
served connections with the incorrect isolation level.
I think this is a JBoss issue (due to JCA) but I'd like confirmation
before submitting a bug to JBoss.
-----Original Message-----
From: Rick DeBay
Sent: Tuesday, July 13, 2004 3:16 PM
To: Firebird-Java@yahoogroups.com
Subject: Pool doesn't clear setReadOnly flag
I'm using connection pooling in a JBoss J2EE container using the
firebirdsql.rar. If I get a connection from the container supplied
datasource and call setReadOnly(true) and return the connection to the
pool by closing it, the next connection served up by the datasource
still has read-only set.
If I use a FBWrappingDataSource directly and open, setReadOnly, close,
and reopen connections, the returned connections are not read-only as is
correct.
I know the new JCA architecture shuffles responsibilities, so my
apologies if this is a JBoss issue.
Rick DeBay
Senior Software Developer
RxStrategies.net
561-650-8195 x-215
If I request connections from the pool and set their isolation level to
greater than READ_COMMITTED, after returning them to the pool I am later
served connections with the incorrect isolation level.
I think this is a JBoss issue (due to JCA) but I'd like confirmation
before submitting a bug to JBoss.
-----Original Message-----
From: Rick DeBay
Sent: Tuesday, July 13, 2004 3:16 PM
To: Firebird-Java@yahoogroups.com
Subject: Pool doesn't clear setReadOnly flag
I'm using connection pooling in a JBoss J2EE container using the
firebirdsql.rar. If I get a connection from the container supplied
datasource and call setReadOnly(true) and return the connection to the
pool by closing it, the next connection served up by the datasource
still has read-only set.
If I use a FBWrappingDataSource directly and open, setReadOnly, close,
and reopen connections, the returned connections are not read-only as is
correct.
I know the new JCA architecture shuffles responsibilities, so my
apologies if this is a JBoss issue.
Rick DeBay
Senior Software Developer
RxStrategies.net
561-650-8195 x-215