activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Updated: (AMQNET-61) Auto-Acknowledgement Mode always sends unnecessary ACK message
Date Wed, 12 Sep 2007 23:55:22 GMT


Jim Gomes updated AMQNET-61:

    Attachment: MessageConsumer.cs.patch.txt

Added a new {{AutoClientAcknowledge}} mode that will put the consumer into client acknowledgment
mode and will send the ACK message automatically.  This is the same action that {{AutoAcknowledge}}
would perform prior to this fix.  I then changed the {{AutoAcknowledge}} mode to *not* send
an ACK message back to the server.

> Auto-Acknowledgement Mode always sends unnecessary ACK message
> --------------------------------------------------------------
>                 Key: AMQNET-61
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client, MSMQ, Stomp
>         Environment: Windows XP SP2
> .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>            Priority: Minor
>         Attachments: IConnection.cs.patch.txt, MessageConsumer.cs.patch.txt, StompWireFormat.cs.patch.txt
> When a MessageConsumer receives a message, it sends a MessageAck even when the acknowledgment
mode is set to AutoAcknowledge.  This results in an error message being sent back to the client
stating that there is no such message to acknowledge.
> According to standard JMS semantics, when AutoAcknowledge mode is used, the client does
not need to (and apparently should not) send back an ACK message.  An ACK message should only
be sent back when the subscription is in ClientAcknowledge or DupsOkAcknowledge mode.  Sending
back unnecessary responses creates unnecessary network traffic and load on a high-speed server.

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

View raw message