Subject Pool doesn't clear setReadOnly flag
Author Rick DeBay
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