This content has been marked as final.
Show 5 replies
-
1. Re: Cannot change transaction isolation level in the middle
beve Sep 14, 2007 8:22 AM (in response to beve)Just some findings...
When we have more then one classification, the first call to DBMessageStoreImpl.redeliver passes without error, but the second call will throw an SQLException when con.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED); is invoked.
Commenting out the setting of the isolation level seems to work but not really an exceptable solution as we don't know why this is happening.
We are using the J2eeConnectionManager.
I'll post back if with any new findings.
/Daniel -
2. Re: Cannot change transaction isolation level in the middle
beve Sep 14, 2007 8:37 AM (in response to beve)Some info about postgres and its transaction isolation levels:
"In postgres, you can use all four possible transaction isolation
levels. Internally, there are only two distinct isolation levels, which
correspond to the
levels Read Committed and Serializable. When you select the level Read
Uncommitted you actually get Read Committed, and when you select
Repeatable Read you really get Serializable, so the actual isolation
level may be stricter than what you select."
/Daniel -
3. Re: Cannot change transaction isolation level in the middle
marklittle Sep 14, 2007 5:07 PM (in response to beve)Daniel, create a JIRA for this so we don't lose it.
-
4. Re: Cannot change transaction isolation level in the middle
beve Sep 16, 2007 9:35 AM (in response to beve)I've created the following jira for this issue http://jira.jboss.com/jira/browse/JBESB-1050
/Daniel -
5. Re: Cannot change transaction isolation level in the middle
kconner Sep 17, 2007 5:09 AM (in response to beve)Thanks Daniel.