Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

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

Solution Unverified - Updated 2011-06-08T00:50:41+00:00 -

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.

Environment

JBoss Enterprise Application Platform (EAP) 5
Hibernate

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)