Duplicate JMS message processing with multiple MessageListener threads

[Haq Yunus]

I am creating a JMS listener application which listens on a queue. I am using TIBCO JMS
implementation and facing an issue that intermittently more than one of my listener threads
pick up a same message and that results in duplicate processing.

Here is how I am creating the connection:

.
	..
	...

	Hashtable<String, String> env = new Hashtable<String, String>();
	env.put(Context.PROVIDER_URL, url);
	env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactoryClass);
	env.put(Context.SECURITY_PRINCIPAL, userName);
	
	String decryptedPass = null;
	//Decryption logic

	try {
		// Look up queue connection factory from naming context.
		if (log.isEnabledFor(Level.DEBUG)) {
			log.debug("Attempting to lookup queue connection factory at '" + 
						this.url + "' as user '" + userName + "'.");
		}
		
		Context ctx = new InitialContext(env);

		QueueConnectionFactory factory = 
			(QueueConnectionFactory) ctx.lookup(connectionFactoryName);
		
		// Create JMS connection using the factory we just looked up.
		if (log.isEnabledFor(Level.DEBUG)) {
			log.debug("Creating queue connection as user '" + userName + "'.");
		}
		connection = factory.createQueueConnection(userName, decryptedPass);
		...
		..
		.

Then here I am creating the listener threads with the same connection created above

//This is called in a loop.
                        // Create a JMS session that is non-transacted, but in client
			// acknowledge mode.  This will allow us to control when
			// messages are acknowledged.
			QueueSession session = 
				getQueueConnection().createQueueSession(
					false, Tibjms.EXPLICIT_CLIENT_ACKNOWLEDGE);
			
			// Create a receiver for the queue we are interested in.  Then
			// set the message listener defined on the outer class.  Messages
			// will be delivered on a dispatcher thread created by the
			// JMS provider.
			Queue queue = session.createQueue(getQueueName());
			session.createReceiver(queue).setMessageListener(getListener());
			...
			..
			.

Now here let us assume, 5 listener threads are created and they listen as receivers on a queue. I am seeing a behavior that
sometime more than one listener thread/receiver picks up the same message and I end up with duplicate processing? How can I
handle it through JMS configuration? Is it even possible? Or I would have to resort to some programmatic solution? Any advise
would be much appreciated. Thanks.

Cross-posted at:http://stackoverflow.com/questions/10191184/duplicate-message-processing-with-multiple-messagelistener-threads

[Prabaharan Gopalan]

May be an obvious thing to ask: But I saw you specify 'Explicit client acknowledge'. But do all your listeners explicitly acknowledge the message reception once they are done? Easy way to check, is there a time difference between the message being processed by the first listener and the second one? Do you have the DUPS_OK_ACKNOWLEDGE setting on?

[Haq Yunus]

Thanks.

Yes , listeners do acknowledge explicitly.

Easy way to check, is there a time difference between the message being processed by the first listener and the second one?
So for this I would have to maintain a map or some mechanism for common repository so listeners can check what message has been processed, right?

DUPS_OK_ACKNOWLEDGE is not on.

[Anurag Verma]

if you are opting for Client Acknowledge while creating Queue Session, the only reason i could see(there may be more) for multiple clients getting the message is the timeout for acknowlegment is less (or may be client is taking much time to acknowledge). Try increasing the timeout for this, atleast upto some value when your client can process the message & acknowledge back. hope that works.