You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Geoff Callender (JIRA)" <ji...@apache.org> on 2009/10/20 13:59:59 UTC

[jira] Updated: (OPENEJB-1091) Cause of RollbackException swallowed

     [ https://issues.apache.org/jira/browse/OPENEJB-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoff Callender updated OPENEJB-1091:
-------------------------------------

    Description: 
This is linked to OPENEJB-782 where the problem was first noted.  The flaw described there still exists in 3.1, ie. the client still has no way of determining the reason a rollback occurred.

When the client digs into the exception cause, all it finds is javax.transaction.RollbackException. The originating javax.persistence.PersistenceException or java.sql.SQLException is missing.

  was:
I can't reopen OPENEJB-782 so I've cloned it.  The flaw described there still exists in 3.1. The client still has no way of determining the cause of the exception.

When the client digs into the exception cause all it finds is javax.transaction.RollbackException. The originating javax.persistence.PersistenceException or java.sql.SQLException is missing.

        Summary: Cause of RollbackException swallowed  (was: CLONE -RollbackException swallowed in TransactionPolicy)

> Cause of RollbackException swallowed
> ------------------------------------
>
>                 Key: OPENEJB-1091
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1091
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.0-beta-2
>            Reporter: Geoff Callender
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> This is linked to OPENEJB-782 where the problem was first noted.  The flaw described there still exists in 3.1, ie. the client still has no way of determining the reason a rollback occurred.
> When the client digs into the exception cause, all it finds is javax.transaction.RollbackException. The originating javax.persistence.PersistenceException or java.sql.SQLException is missing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.