Mailing-List: contact commits-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openejb.apache.org
Date: Mon, 25 Apr 2011 11:24:05 +0000 (UTC)
From: "Vamsavardhana Reddy (JIRA)" <jira@apache.org>
To: commits@openejb.apache.org
Message-ID: 
 <1052601623.79678.1303730645815.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OPENEJB-1091) Cause of RollbackException
 swallowed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENEJB-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024775#comment-13024775 ] 

Vamsavardhana Reddy commented on OPENEJB-1091:
----------------------------------------------

David,

I think you are referring to org.apache.openejb.client.EJBInvocationHandler.convertException() and org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException() methods.  As per the patch, if we change the exceptions to LocalExceptions in TransactionPolicy class, then these convertException methods should be converting those to remote exceptions in case of remote invocation.

> 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: Jean-Louis MONTEIRO
>             Fix For: 3.0
>
>         Attachments: open-ejb_1091.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira