We are currently experiencing a problem where are consumers are not always being released when we shutdown our consumers. This seems to happen less than half the time, but does force us to restart at least one of the 2 ActiveMQ servers that we have in our Shared File System Master Slave cluster. We are using the new AMQ persistence. Because we normally have 2 consumers, we see the problem because every third message hangs while it waits to find the dead consumer.
We are currently using the snapshot build apache-activemq-5.1-20080116.172744-2 on linux. We needed the snapshot build to get the MasterSlave fix for AMQPersistenceAdapter. We are also using Jencks on the consumer side. The jars we are using for ActiveMQ are 5.0.0. I am not sure if it relates to the following bug: https://issues.apache.org/activemq/browse/AMQ-1376 Thanks, Mike M -- View this message in context: http://www.nabble.com/Consumers-not-always-being-released-tp15818936s2354p15818936.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
