[
https://issues.apache.org/jira/browse/AMQNET-591?focusedWorklogId=293756&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293756
]
ASF GitHub Bot logged work on AMQNET-591:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Aug/19 09:05
Start Date: 13/Aug/19 09:05
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #14: AMQNET-591:
Transactions support
URL: https://github.com/apache/activemq-nms-amqp/pull/14#issuecomment-520753478
@cjwmorgan-sol i think the current workaround is safer, than setting
something arbitarily, that may cause other unexpected issues. At the end of the
day this is only temp until AMQPNetlite release.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 293756)
Time Spent: 4.5h (was: 4h 20m)
> 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
> Priority: Major
> Time Spent: 4.5h
> 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
(v7.6.14#76016)
