MQSeries.net :: View topic - QueueConnection, ConnectionConsumer stop/close problem

griffel · Posted: Tue Mar 22, 2005 6:08 am Post subject:

We've used WebSphere MQ 5.3 CSD6 for Windows (here 2000) as a Java JMS 1.0 client to connect to a queue manager running as WebSphere MQ 5.3.1 on z/OS via SVRCONN-channels.

Our code included a shutting-down sequence like:

connection.stop(); // to avoid further delivery of messages to our application

try {
if (consumer != null) {
consumer.close(); // clean-up ressources
}
} finally {
consumer = null;
}

connection.close(); // not needed any longer

The consumer has a message selector to receive only some specific messages.

Everything worked as designed. Then, we've switched to CSD9 on our client. Afterwards, shutting-down and going alive again within our client, resulted in all messages from the queue the consumer listens on being received by a new consumer on the restarted connection, even though it has it own distiguished message selector set.

After changing our code to

try {
if (consumer != null) {
consumer.close();
}
} finally {
consumer = null;
}

connection.stop();
connection.close();

everything works fine again.

Bug or feature?