[
https://issues.apache.org/jira/browse/AMQ-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac updated AMQ-2093:
-------------------------------
Fix Version/s: (was: 5.4.2)
5.5.0
> Message Selector Not working in High Load.
> ------------------------------------------
>
> Key: AMQ-2093
> URL: https://issues.apache.org/jira/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: KumarMarkkaSagayam
> Fix For: 5.5.0
>
>
> 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.
