Return-Path: 
 <dev-return-27538-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 C73A64053
	for <apmail-activemq-dev-archive@www.apache.org>;
 Sat,  9 Jul 2011 20:54:24 +0000 (UTC)
Received: (qmail 60291 invoked by uid 500); 9 Jul 2011 20:54:24 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 60244 invoked by uid 500); 9 Jul 2011 20:54:23 -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 60236 invoked by uid 99); 9 Jul 2011 20:54:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jul 2011 20:54:23 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
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; Sat, 09 Jul 2011 20:54:21 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id B3A85410BD
	for <dev@activemq.apache.org>; Sat,  9 Jul 2011 20:53:59 +0000 (UTC)
Date: Sat, 9 Jul 2011 20:53:59 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <409187290.261.1310244839717.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <17174292.220411294435246392.JavaMail.jira@thor>
Subject: [jira] [Updated] (AMQ-3123) ajax client receives incorrect messages
 when subscribed to multiple topics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Timothy Bish updated AMQ-3123:
------------------------------

    Fix Version/s: NEEDS_REVIEWED

> ajax client receives incorrect messages when subscribed to multiple topics
> --------------------------------------------------------------------------
>
>                 Key: AMQ-3123
>                 URL: https://issues.apache.org/jira/browse/AMQ-3123
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.2
>            Reporter: Alex Dean
>             Fix For: NEEDS_REVIEWED
>
>         Attachments: undelivered_messages_need_associated_consumer.patch
>
>
> When an ajax client is subscribed to multiple topics, the "id" attribute of a returned <response> element indicates to JavaScript which callback function should process the message.  Currently, the MessageListenerServlet returns multiple copies of each message, 1 per subscription.  So all callback functions will receive all messages.
> For example, if I send messages 'A1' and 'A2' to /topic/topicA, and messages 'B1' and 'B2' to /topic/topicB, my ajax client gets the following message:
> <ajax-response>
>   <response id='handlerA' destination='topic://topicA' >A1</response>
>   <response id='handlerA' destination='topic://topicA' >B1</response>
>   <response id='handlerA' destination='topic://topicA' >A2</response>
>   <response id='handlerA' destination='topic://topicA' >B2</response>
>   <response id='handlerB' destination='topic://topicB' >A1</response>
>   <response id='handlerB' destination='topic://topicB' >B1</response>
>   <response id='handlerB' destination='topic://topicB' >A2</response>
>   <response id='handlerB' destination='topic://topicB' >B2</response>
> </ajax-response>
> Further, these messages are constantly re-delivered to the client.  (They are never removed from the unconsumedMessages linked list in AjaxListener.)
> If https://issues.apache.org/jira/secure/attachment/12467757/all_messages_are_delivered_to_ajax_clients.patch from https://issues.apache.org/jira/browse/AMQ-3094 is applied, the duplication is reduced, but the "id" values for the "topicB" messages are still incorrect.
> <ajax-response>
>   <response id='handlerA' destination='topic://topicA' >A1</response>
>   <response id='handlerA' destination='topic://topicA' >B1</response>
>   <response id='handlerA' destination='topic://topicA' >A2</response>
>   <response id='handlerA' destination='topic://topicA' >B2</response>
> </ajax-response>
> I've attached a test which demonstrates the problem.  This patch will conflict with the one attached to AMQ-3094, but the conflicts should be easy to resolve.

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