[
https://issues.apache.org/activemq/browse/AMQNET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63040#action_63040
]
Alexandre Gallice commented on AMQNET-290:
------------------------------------------
Thanks for answer.
I understand that enlisting as a durable resource manager is difficult.
My only concern is about the side effects. I don't understand what's happening
when the code using NMS crashes in the middle of a transaction ?
Do we lose the message ? Is the transaction aborted ?
Thanks again for the snapshot, I should be able to test it next week.
> Add an API model to NMS that allows providers to participate in Distributed
> Transactions.
> -----------------------------------------------------------------------------------------
>
> Key: AMQNET-290
> URL: https://issues.apache.org/activemq/browse/AMQNET-290
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: NMS
> Affects Versions: 1.4.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.0
>
>
> Currently the NMS API doesn't define any way for the client to participate in
> distributed transactions. The JMS model allows a for this using the Java XA
> transactions. The JMS API defines an XAConnectionFactory, XAConnection, and
> XASession that provide the needed bits to interact with a Transaction Manager.
> We should provide something similar in NMS that allows for a provider library
> like NMS.ActiveMQ to be used in distributed transactions in .NET most likely
> using the MSDTC. The API could expose an IEnlistmentNotification
> implementation that allows the client to enlist the Transaction in a DTC
> controlled transaction as a Resource Manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
