But system vs application exceptions is about whether the container has to
commit or rollback the transaction. In this error case the transaction is
not handled at all.
I can see that in tomee it's handled for EJB. You can see that
EjbTransactionUtil.afterInvoke is always invoked in the finally
I think it's related to the definition of System versus Application
exception per specification. I would need to check again as I don't recall.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Fri, Dec 2, 2022 at 11:58 PM Vicente Rossello
wrote:
> Hi,
>
Hi,
I've tried a patch catching Throwable and it works as expected, with CDI
closing the transaction and Eclipselink not getting bugged. I think this
should be part of tomee. Is there any reason for this Interceptor for not
catching StackOverflowError or an AssertionError and leaving the
Hi,
We are using tomee with JPA and eclipselink implementation, in latest tomee
8.0.
Whenever we have a StackOverflowError (very rare case, fortunately :) ),
the application server is in an inconsistent state, with eclipselink
throwing some random errors, we have to shut the instance down.
I
