[
https://issues.apache.org/jira/browse/OPENEJB-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562911#action_12562911
]
Manu T George commented on OPENEJB-702:
---------------------------------------
Missed a few words above
----------------------------------------
David J. Being an activeMQ committer and the writer of the G Transaction
manager it would be great if you could review the fix. I have verified that the
tests work against the openejb codebase at the time I created the patch but my
knowledge of both the Geronimo TM and AMQ are not as good as I would like it to
be. I can reverify and post a new patch if you want.
I can reverify and get this into openejb provided someone gets the activemq
patch committed. We will also ideally need a new release of AMQ 4 with the
related patch (When is the next AMQ 4.x release)
Another approach would be to upgrade to AMQ 5.0.(I believe Dain was planning to
work on that but I think not for this release).
> 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
> Fix For: 3.0.x
>
> 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.
