scrollable/updateable PreparedStatement bug in jBoss 2.4.4

[thomasp]

[This is a crossposting from the jBoss database/persistence forum, since I did not get a reply there]

Hello to everybody,

I have a problem when using BMP and ORACLE, it seems that jBoss 2.4.4 prevents me from using scrollable or updateable prepared statements. This is my jboss.jmcl:


OracleDB
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl

my url
1200000
SIGNSOFT_thomas
thomas
5
false
false
false
true
120000
1800000
false
false
1.0
0


I'm opening now a connection on that datasource from within a bean using ds.lookup() for the data source, I also request a scrollable result set. This does not work, because org.jboss.pool.jdbc.PreparedStatementFactory.createObject() does not care if I request an updateable or scrollable result set.

My question: is there any workaround beside writing my own MBean around my own XADatasource implementation? The current CVS version has no newer files, and I cannot use jBoss 3.0 since it is alpha software.

Thank you,

Thomas

[johnnycannuk]

Yeah this is a bug....

Check out http://main.jboss.org/thread.jsp?forum=46&thread=7336

I posted the fix details and link to the patch there.

Mike

[thomasp]

Mike,

thank you very much for your answer. I already thought it would be some stuff like that. I'm currently fighting with small-size pools, it seems it does not release my connection. That's going to be a little bit more funny...

Thomas

[thomasp]

Sorry Mike,

I just wanted to mention that with this patch you do not use the pool anymore. But another fix would be bigger, I think ;)

Thank you

[davidjencks]

You can get the oracle (or whatever) connection from the jboss wrapper by calling ((JDBCConnection)conn).getUnderlyingConnection(), and do what you like with it. When you are done, be SURE to close the jboss connection, not the Oracle one, or you will be very sorry. Be sure to release all resources quickly to minimize the chances of interfering with the pooling.

This won't use the prepared statement caching of the jboss wrappers, but the Oracle driver's caching is probably better anyway.

[johnnycannuk]

Thomasp

If my fix doesn't use the pool, then none of the other calls to createStatement or prepareCall do either...my imlementation is a cut and paste of createStatement style...

Mike