[jira] Closed: (OPENEJB-702) Transaction Logging not working in OpenEJB for MDBs

["David Jencks (JIRA)" <ji...@apache.org>]

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

David Jencks closed OPENEJB-702.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.0.x)
                   3.0
         Assignee: David Jencks

I simplified the patch a bit.  After some thought I realized that only the activemq vm transport is broken and switching to tcp transport lets all the openejb tests pass.

rev 637368 applied to trunk.

> Transaction Logging not working in OpenEJB for MDBs
> ---------------------------------------------------
>
>                 Key: OPENEJB-702
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-702
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: container system
>    Affects Versions: 3.0
>         Environment: All
>            Reporter: Manu T George
>            Assignee: David Jencks
>             Fix For: 3.0
>
>         Attachments: OPENEJB-702.patch
>
>
>   I was investigating GERONIMO-3354. Found that the exception
> getting thrown was due to an XAResource getting passed to the the
> geronimo transaction manager instead of a NamedXAResource .
> To fix this we need to change the method  
> public MessageEndpoint createEndpoint(XAResource xaResource) throws UnavailableException in
> org.apache.openejb.core.mdb.EndpointFactory
> In this method in the case of using the Geronimo Transaction Manager we need to pass a NamedXAResource if we need transaction logging to function.
> Directly passing a NamedXAResource will fix this problem at the openEJB side for now but we need to bring in a layer of abstraction since the NamedXAResource is a geronimo TM specific class and in OpenEJB standalone the TM must be pluggable.
> For the time being its acceptable to use NamedXAResource. 
> This requires a fix in AMQ also to work . The JIRA in question is 
> https://issues.apache.org/activemq/browse/AMQ-1438

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