activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-217) AcknowledgementMode.Transactional Broken (Apache.NMS.NMSException: Invliad State: Not Currently in a Transaction)
Date Thu, 10 Dec 2009 15:45:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56362#action_56362
] 

Timothy Bish commented on AMQNET-217:
-------------------------------------

The behaviour of throwing an error when you commit a Session that has already been committed
is correct, a new transaction is not started until a new message is sent or received on the
session.

The Producer should send to the given destination if you call producer.send(dest, message)
but that will not overwrite the destination that was set when the producer was created and
the next time you call producer.send(message) the message would be sent to the originally
assigned destination.  If that is not working then please open a new issue and submit a test
case to demonstrate that problem.

> AcknowledgementMode.Transactional Broken (Apache.NMS.NMSException: Invliad State: Not
Currently in a Transaction)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-217
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-217
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.2.0
>         Environment: Win XP  SP3 , Windows 2003 Server, Windows 2008 server
>            Reporter: Michel Van Hoof
>            Assignee: Jim Gomes
>
> One of our application that is using the NMS library was upgraded to 1.2.0.0-RC1 for
testing. Same code working nicely with 1.1.0.0 all of the sudden started to return errors
stating that the session is not in transactional mode altough this is the case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message