Return-Path: 
 <dev-return-26702-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2D9674276
	for <apmail-activemq-dev-archive@www.apache.org>;
 Fri, 13 May 2011 20:24:28 +0000 (UTC)
Received: (qmail 1687 invoked by uid 500); 13 May 2011 20:24:28 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 1648 invoked by uid 500); 13 May 2011 20:24:27 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 1640 invoked by uid 99); 13 May 2011 20:24:27 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 20:24:27 +0000
X-ASF-Spam-Status: No, hits=-1998.7 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD,URI_HEX
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 20:24:26 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 8688C89B44
	for <dev@activemq.apache.org>; Fri, 13 May 2011 20:23:47 +0000 (UTC)
Date: Fri, 13 May 2011 20:23:47 +0000 (UTC)
From: "Marcel Casado (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <843211007.11180.1305318227547.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <186307549.8510.1305240947923.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (AMQ-3320)
 ActiveMQ.Advisory.MessageConsumed.TempQueue and AMQ.A.MC.Queue Topics
 receive advisory messages when TQ or Queue are purged
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/AMQ-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032740#comment-13032740 ] 

Marcel Casado edited comment on AMQ-3320 at 5/13/11 8:22 PM:
-------------------------------------------------------------

Added testTempMessageConsumedAdvisoryConnectionClose() method to test this issue. The test should fail since the test expects no new advisories when the connection is closed 

      was (Author: marcelcasado):
    Added testTempMessageConsumedAdvisoryConnectionClose() method to test this issue. The test should fail since the test expects no new advisories when the connection is close 
  
> ActiveMQ.Advisory.MessageConsumed.TempQueue and AMQ.A.MC.Queue Topics receive advisory messages when TQ or Queue are purged
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3320
>                 URL: https://issues.apache.org/jira/browse/AMQ-3320
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.2, 5.5.0
>            Reporter: Marcel Casado
>            Priority: Minor
>         Attachments: AdvisoryTempDestinationTests.java
>
>
> I have enabled <policyEntry tempQueue="true" advisoryForConsumed="true" /> in the broker so I can subscribe to "ActiveMQ.Advisory.MessageConsumed.TempQueue.>" to get notified of messages consumed on a tempQueue/s. When client shuts down 
> if remaining messages are in the tempQueue an advisory message is generated and send to the ActiveMQ.Advisory.MessageConsumed.TempQueue topic for each message for that tempQueue. The same will happen if purge() is called on a TempQueue or Queue for example through JMX.  
> In my application I need to know if a message is consumed by a client but I can not differentiate between a client "ack" massage and one "ack" by the broker when the tempQueue is "disposed" looking to the message sent to the ActiveMQ.Advisory.MessageConsumed.TempQueue... . 
>  
> Looking at the code for TempQueue and Queue this is the sequence :
> TempQueue.dispose(context) --> purge() --> removeMessage() -> acknowledge() --> messageConsumed() 
> This is kind of a conceptual issue since myself consider that removing a message due a purge or a tempQueue cleanup should not trigger a messageConsumed advisory.
> Original ActiveMQ users post : http://activemq.2283324.n4.nabble.com/ActiveMQ-Advisory-MessageConsumed-TempQueue-problem-td3510067.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira