In Hibernate / transactions an 'Already marked for rollback' exception does not include the root cause

Issue

• When we call an exception from within the transaction border, JBoss or/and Hibernate catches the exception an rewrites it as a 'already marked for rollback' exceptions. That is ok because it is part of the spec. The problem is that the new exception does not include the real cause for the exception. That eliminates the possibility for us to extract the cause from the exception and write the error message.