activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] Updated: (AMQNET-124) Irregular Behavior When Using Commit and Rollback on Non-Transacted Queue
Date Mon, 01 Dec 2008 20:10:05 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Gomes updated AMQNET-124:
-----------------------------

    Fix Version/s: 1.2

> 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.2
>
>
> 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.


Mime
View raw message