[
https://issues.apache.org/activemq/browse/AMQNET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47364#action_47364
]
Jim Gomes commented on AMQNET-124:
----------------------------------
Yes, an exception should definitely be thrown here. I'm surprised that it
isn't.
Could you provide a small snippet of code that exposes this behavior? If you
want, you could even add it as a test case to the unit tests. Otherwise, I can
add it to the test cases. I wouldn't want this to creep up again. Thanks!
> 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
>
> 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.
