JBOSS 2.4.4 / Informix 7.31 cannot change Isolation Level or

[jschimmoeller]

HELP!!!!!

We are using Jboss 2.4.4 with tomcat 4.0.1. We want to be able to change the isolation level from committed read to dirty read and also change the lock mode from no wait to wait for 30 seconds. We are using a connection pool and configuration of the pool is below. As you see, we have set the TransactionIsolation to read uncommitted and set blocking to true however when I review the connections via informix using a "onstat -g sql" they are still committed read and no wait.

I see that there is other using informix and jboss do you have any answers.

Jim


com.informix.jdbc.IfxDriver



NetADS
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl
jdbc:informix-sqli://netaserv:22386/netanalytics:INFORMIXSERVER=netaservshm</at
tribute>
netauser
netauser
50
10
true
true
true
true
30000
120000
1800000
true
true
0
TRANSACTION_READ_UNCOMMITTED

[jschimmoeller]

Problem solved.

IBM gave me a new JDBC driver 2.21 JC3 x1 that allows you to change the isolation level and lock mode via the DBURL.

Jim

[lafr]

I use the same Informix Server and JDBC-Driver.
But I did not find this in the documentation.

Can you show us an example how you can set this properties ?

[smorrell]

> Can you show us an example how you can set this
> properties ?


Contact IBM to get the version 2.21 JC3 x1 of the JDBC driver. Then use the IFX_LOCK_MODE_WAIT and/or IFX_ISOLATION_LEVEL property in the URL. Like this...

jdbc:informix-sqli://host:port/db:informixserver=value;IFX_LOCK_MODE_WAIT=30

[micah_gideon]

This configuration parameter appears to be ignored, so I wrote a simple MBean to function as a startup class. It simply retrieves the MaxSize of your connection pool, retrieves that number of connections and sets their lock wait modes and then closes them. It is sub-optimal as it's effective usage requires you to set the connection pool's MaxSize equal to the MinSize.

Installation requires that you locate the attached .SAR in your deploy directory and the above mentioned MaxSize=MinSize modification in informix-service.xml.

I hope someone finds this useful. The attached .SAR includes the full source if you'd like to take a look - it's also a decent example of a JBoss MBean.

[micah_gideon]

This configuration parameter appears to be ignored, so I wrote a simple MBean to function as a startup class. It simply retrieves the MaxSize of your connection pool, retrieves that number of connections and sets their lock wait modes and then closes them. It is sub-optimal as it's effective usage requires you to set the connection pool's MaxSize equal to the MinSize.

Installation requires that you locate the attached .SAR in your deploy directory and the above mentioned MaxSize=MinSize modification in informix-service.xml.

I hope someone finds this useful. The attached .SAR includes the full source if you'd like to take a look - it's also a decent example of a JBoss MBean.

[micah_gideon]

This configuration parameter appears to be ignored, so I wrote a simple MBean to function as a startup class. It simply retrieves the MaxSize of your connection pool, retrieves that number of connections and sets their lock wait modes and then closes them. It is sub-optimal as it's effective usage requires you to set the connection pool's MaxSize equal to the MinSize.

Installation requires that you locate the attached .SAR in your deploy directory and the above mentioned MaxSize=MinSize modification in informix-service.xml.

I hope someone finds this useful. The attached .SAR includes the full source if you'd like to take a look - it's also a decent example of a JBoss MBean.

[micah_gideon]

i apologise for the multiple posting. i was recieving errors during posting and when i tried to check, my post did not show up.