You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Michael Andre Pearce (Jira)" <ji...@apache.org> on 2019/10/03 09:52:01 UTC
[jira] [Resolved] (AMQNET-591) Transactions Support
[ https://issues.apache.org/jira/browse/AMQNET-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce resolved AMQNET-591.
-----------------------------------------
Resolution: Fixed
> Transactions Support
> --------------------
>
> Key: AMQNET-591
> URL: https://issues.apache.org/jira/browse/AMQNET-591
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: AMQP, NMS
> Reporter: Krzysztof Porebski
> Assignee: Michael Andre Pearce
> Priority: Major
> Fix For: 1.8.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> A session may be optionally specified as transacted. Each transacted
> session supports a single series of transactions. Each transaction groups a
> set of produced messages and a set of consumed messages into an atomic
> unit of work. In effect, transactions organize a session’s input message
> stream and output message stream into a series of atomic units. When a
> transaction commits, its atomic unit of input is acknowledged and its
> associated atomic unit of output is sent. If a transaction rollback is done,
> its produced messages are destroyed and its consumed messages are
> automatically recovered.
> A transaction is completed using either its session’s Commit() or
> Rollback() method. The completion of a session’s current transaction
> automatically begins the next. The result is that a transacted session
> always has a current transaction within which its work is done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)