|
Jim Richards and others reported problems with
exceptions not causing rollbacks ... my colleagues and I have seen all the same
symptoms reported here so far. Exceptions that occur during a 'set' method on
a container managed entity bean do not get
propogated up to the caller (we put in Anton's suggested patch to allow a
rollback, but the exception cannot be thrown back since the 'beforeCompletion'
method is a defined in teh Synchronization EJB interface that does not throw
exceptions), and exceptions thrown from a container managed method with
TX_REQUIRED etc. do not cause a rollback (similar to the scenario reported by
Jim Richards 10/23).
The 'set method' problem Helene is looking
into.
The exceptions not causing rollbacks I have worked
around by making my methods bean managed and handling rollback in exceptions
myself .. luckily the only isues I have are in Session beans, so my entities can
still be container managed. From Jom's email, it looks as if rollbacks would
need to be added to the generated BullBean code to be set in each catch around
the defined methods, maybe. As this code is generated, we cannot really put in a
reliable patch without having to re-add it every time the bean is re-built. It
needs to be added to the Jonas generation mechanism, or somewhere else in the
architecture that perhaps I have missed. Is Bull looking into this
?
Thanks,
Caroline.
|
