Hi Gary, thanks for responding quickly! I have both run and coded trivial prducer consumer programs without issue. Comparing and constrasting their code to my current application, my application is more sophisticated with multiple producer and consumer threads running in differnt processes. There are therefor multiple sessions per connection, one for each thread, although each program instance uses a single connection. Selectors are also being used (in a very basic way) to filter messages for consumers. Beyond that, other than packaging the JMS code in an abstraction layer to hide it from the rest of the application, i cannot see any major differences.
The key behaviour to note is that upon the producer terminating its JMS connection the consumers immidiatly recieve their messages as expected. Indeed according the the ActiveMQ interface the messages are on the queue even prior to the producer hanging up its connection, its just the consumers remain blocked waiting to recieve them. Given this behaviour arrises now that i am using multiple sessions, could i be running fowl of some broker flow control settings? (I have read this can cause haning behavior, however the cases i saw in the docs dont seem to exactly match this) Thanks for your time, Chris -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Messages-not-consumed-till-producer-connection-close-tp3985842p3986855.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
