Gunnar Hilling wrote:
When trying code i catch exception and do a tx.abort() when an error occurs. But when the error is caused by an SQLException during tx.commit() all changes done are written to the database...
this is a real problem for me. Shouldn't the db-commit be "all or nothing" (rc5, postgres).
Of course this should be the case. There is a bug in conjunction with proprietary TransactionExt#flush() method (OJB find new inserted objects in default cache implementation after abort). Workaround till fix could be to change the used ObjectCache from ObjectCacheDefaultImpl to ObjectCachePerBrokerImpl.
Or you have wrong 'useAutoCommit' setting in your jdbc-connection-descriptor? Default was 1.
regards, Armin
-Gunnar
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
