Re: large transaction sizes and rollbacks
"Justin T. Sampson" <[email protected]>
| Newsgroups | gmane.comp.java.prevayler |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Mar 5, 2011 at 7:23 AM, <[email protected]> wrote: > I think this was the reason I was confused about why prevayler was > silently ignoring exceptions thrown at that point. I was expecting > prevayler to stop all further processing. What heppens if, for example, > you get an OutOfMemoryException at this point? Well, that's actually OutOfMemory*Error*, not OutOfMemoryException. Prevayler treats Errors as nondeterministic events, precisely because things like OutOfMemoryError and StackOverflowError can't be guaranteed to not occur even with perfectly written code. So indeed, Prevayler stops all further processing on encountering an Error during either original execution or journal replay. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion _______________________________________________ "Databases in Memoriam" -- http://www.prevayler.org