GlorpWriteFailure and GlorpTransactionFailure

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

GlorpWriteFailure and GlorpTransactionFailure


I am a bit confused about GlorpWriteFailure and GlorpTransactionFailure.

From what I found and what I read in the source code, an optimistic locking failure should throw a GlorpTransactionFailure. But in VAST, I always get a GlorpWriteFailure. There are two References to GlorpWriteFailure and one to GlorpTransactionFailure and all of them could be optimistic locking problems or others. I must say I've never actually gotten a GlorpTransactionFailure, but GlorpWriteFailure is quite common.

Glorp sometimes just swallows SQL errors and just signal one of these two exceptions.

So it is hard to tell if an update failed because of an optimistic locking failure or something else if I only get a GlorpWriteFailure wihout much additional info.

How do people handle this? Are there any best practices available anywhere?

Thanks for your ideas


You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at
For more options, visit