[AMQ-2093] Message Selector Not working in High Load.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.0, 5.0.0, 5.2.0
• Fix Version/s: 5.6.0
• Component/s: Broker

Environment

Windows XP Profesional - 32 Bit.
JDK 1.5 Update 8
Broker Running in Jboss

• Assignee: Unassigned
• Reporter: Kumar
• Created: 02/Feb/09 11:28
• Updated: 20/Sep/11 11:01
• Resolved: 20/Sep/11 11:01

Description

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