[jira] [Work logged] (AMQNET-591) Transactions Support

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQNET-591?focusedWorklogId=286780&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-286780 ]

ASF GitHub Bot logged work on AMQNET-591:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Aug/19 15:47
            Start Date: 01/Aug/19 15:47
    Worklog Time Spent: 10m 
      Work Description: cjwmorgan-sol commented on issue #8: AMQNET-591: Transactions support
URL: https://github.com/apache/activemq-nms-amqp/pull/8#issuecomment-517344936
 
 
   I've been taking a look at the source code changes there look alright to me.
   I've starting testing against two brokers, one that supports transactions (activemq artemis 2.9.0) and one that does not (solace broker).
   It has taken me some sometime to verify the changes as I've some run into issues that I think are unrelated to the transport support, at least on the solace broker, that could be fixed.  (not sure if this is the right place to discuss those though)
   I tried out the transaction sample which worked however the tests did not. I'm not sure why the interop tests do not work. None of the test seem to receive the message from the transaction.
   
   @HavretGC Have you tried the tests against a broker, or is that why you raise #9 ?
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 286780)
    Time Spent: 20m  (was: 10m)

> 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: 20m
>  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)