[
https://issues.apache.org/activemq/browse/AMQNET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-124.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.1
I added several new unit tests to test calling transaction methods (Commit,
Rollback) on a non-transacted session. They all throw the expected exception
and appear to be functioning correctly. I am resolving this item unless a
counter-example can be coded into a unit test that shows failure.
> Irregular Behavior When Using Commit and Rollback on Non-Transacted Queue
> -------------------------------------------------------------------------
>
> Key: AMQNET-124
> URL: https://issues.apache.org/activemq/browse/AMQNET-124
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ Client
> Affects Versions: 1.2
> Environment: Windows, Latest Code from Subversion database
> Reporter: Christian Gross
> Assignee: Jim Gomes
> Fix For: 1.1
>
>
> If I instantiate a queue and then listen to it as non-transacted (eg not
> using AcknowledgementMode.Transactional), and then after processing a message
> call either session.Commit() or session.Rollback() I get REALLY random
> behavior.
> Sometimes messages don't appear. Sometimes messages appear, but they are the
> old messages even though within the queue it is a new message.
> I know that I should not be calling a transactional method on a
> non-transactional queue, but I thought an exception would be warranted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
