activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuvaraj Vanarase <>
Subject RE: JMS Messages not consumed till producer connection close :-(
Date Fri, 04 Nov 2011 06:42:09 GMT
Well, few details if you haven't checked/you could provide:

-- produce/consumer are on same JVM?
-- do they create separate connections?
-- do they do connection.start() after creating connection?

Why don't you just try with single producer and consumer to make sure there is no threading
Why don't you try without filter if something is wrong over there?


Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
- Top 15 Best IT Employers for 5 consecutive years (link).
- Celebrating 10 Years!

-----Original Message-----
From: PinkyNoBrain [] 
Sent: Thursday, November 03, 2011 7:00 PM
Subject: JMS Messages not consumed till producer connection close :-(

I previously posted this question on StackOverflow and was advised to raise
it here after no obvious solutions where found.

I am relatively new to JMS and have encountered a weird problem implementing
my first real application so please excuse me if this turns out to be a
rookie implementation/configuration mistake. I'm desporate for any help or

Background: I use AtiveMQ (java) as the message broker with non-transacted,
non-persitent queues.

The Design: I have a straight forward producer/consumer system based around
a single queue, a producer program with a number of producer threads and s
seporate consumer program with an number of consumer threads. Selectors are
used to filter which messages a node recieves.

The Problem: The producers succesfully places their items on to the queue (i
have verified they are there using the web interface) however the consumers
remain blocked and do not read them. Only when i close the JMS connection in
the producer do the consumers jump into life and consume the messages as

This bevaior seems very weird to me, surely you shouldnt have to completely
hang up the producer connection for the consumers to be able to read from
the queue. I must have made a mistake somewhere(possibly with sessions) but
the at the moment the number of things that could be wrong is to large and i
have no idea what would cause this behaviour.

Any hints as to a solution, the cause of the problem or just how to continue
debugging would be greatly appreciated.

Thanks for your time,

P.S If you requrie any additional information i am happy to provide it

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message