Cannot change transaction isolation level in the middle of a

[beve]

Hi,

we are getting this message when there are several messages in the message store with the same classification:

2007-09-14 10:08:05,376 DEBUG [org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl] Deadlocks may occur under normal processing
2007-09-14 10:08:05,376 DEBUG [org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl] Cannot change transaction isolation level in the middle of a transaction.
org.postgresql.util.PSQLException: Cannot change transaction isolation level in the middle of a transaction.
 at org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733)
 at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.setJdbcTransactionIsolation(BaseWrapperManagedConnection.java:534)
 at org.jboss.resource.adapter.jdbc.WrappedConnection.setTransactionIsolation(WrappedConnection.java:390)
 at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.redeliver(DBMessageStoreImpl.java:318)
 at org.jboss.soa.esb.actions.MessageRedeliverer.process(MessageRedeliverer.java:74)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265)
 at org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:108)
 at org.jboss.soa.esb.schedule.ScheduleProvider$ESBScheduledJob.execute(ScheduleProvider.java:212)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

As you can probably see the database we are using is postgres.
Has anyone seen this before?

Thanks,

Daniel

[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

[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

[marklittle]

Daniel, create a JIRA for this so we don't lose it.

[beve]

I've created the following jira for this issue http://jira.jboss.com/jira/browse/JBESB-1050

/Daniel

[kconner]

Thanks Daniel.