I have a camel-ibatis app that polls an oracle database table for inserted rows and uses the onConsume option to update the table with a "row consumed" column to avoid duplicate polling. Everything works except the update statement for the onConsume throws "READ_COMMITTED and SERIALIZABLE are the only valid transaction levels" How do I get around this? I noticed that the Class DefaultIBatisProcessingStategy has a hard coded transaction level of Connection.TRANSACTION_REPEATABLE_READ. It looks like this Class was Unit tested with MySQL. Is there some way that I can configure it differently from the Oracle database side or is it possible to request that the Transaction Isolation Level be a configurable element in the camel-ibatis configuration as an enhancement? Any ideas or suggestions are welcome. Thanks.
-- View this message in context: http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html Sent from the Camel - Users mailing list archive at Nabble.com.
