Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1221622409.1247831014941.JavaMail.jira@brutus>
Date: Fri, 17 Jul 2009 04:43:34 -0700 (PDT)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2093) Message Selector Not working in High
 Load.
In-Reply-To: <1727199431.1233574139418.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Rob Davies commented on AMQ-2093:
---------------------------------

Can you attach a junit test case please ?

> Message Selector Not working in High Load.
> ------------------------------------------
>
>                 Key: AMQ-2093
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2093
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.0, 5.0.0, 5.2.0
>         Environment: Windows XP Profesional - 32 Bit.
> JDK 1.5 Update 8 
> Broker Running in Jboss
>            Reporter: Kumar
>            Priority: Blocker
>
> I am facing a problem on receiving messages by multiple blocked receivers from a single Queue with different correlation id.
> Here is what exactly I am doing.
> My client thread is publishing a message ( having a unique co-relationid) to a RequestQueue and waiting for a response (blocked)
> on Response Queue with the same co-relationid.  I have such 100 client threads.
> The client thread is publishing a message using normal JMS (w/o Spring) whereas receiving the response using Spring JMSTemplate
> using object=jmsQueueTemplate.receiveSelectedAndConvert(destinationName, "JMSCorrelationID='" + correlationID+ "';
> the other side, Spring Message POJOs are consuming the published message from RequestQueue, processing it and sending back the response to ResponseQueue with the co-relation id set using normal publishing (w/o Spring).
> My Observations
> I have sent 1000 unique co-relationId messages (using 100 client threads) but received 992 unique co-related id messages;
> 8 duplicated co-related id messages and dropped 8 unique co-related id messages.
> This is happening under 100 client threads load using Jmeter 

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