Does isolation has change in 3.2.2 ?

[sbocquet]

Hi all,

We have an application that use an Informix database. Before each SELECT statement with our DAO framework, we set the isolation mode to dirty read, while the standard isolation for our EJB (UPDATE and DELETE) is pessimist lock.
When we deploy in with JBoss 3.2.1, all is fine... but when we deploy it with JBoss 3.2.2, at the first SELECT SQL request, we have this error :
You cannot set isolation level during a managed transaction!

Can someone tell me what's going on with 3.2.2 ?

Thanks

[sbocquet]

Hi,

I need to be in TRANSACTION_READ_COMMITTED with my EJB, but also have a DAO that need to be in TRANSACTION_READ_UNCOMMITTED, in order not to block the users during the SELECT statements (because of long EJB updates in the databases)...

It seems that with the 3.2.2 version, the isolation level of a database connection cannot be changed (3.2.1 and 3.2.0 is possible !). The following code returns an SQL isolation error...

myConnection.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);

Is it right?
Why can we do this with 3.2.1 and not with 3.2.2 ? A bug ?
Finally, is there a solution to change the isolation level ?

Please, helppppppp....

[snanduri]

hi,
I am facing the same problem, when i switched over to 3.2.3 version, the code is failing with the "You cannot set isolation level during a managed transaction" error.
Anyone, please address this issue, this is critical for us too
Steve