I am running some point-to-point performance tests using the latest SwiftMQ and notice that when the test is over and the code calls the QueueConnection.close() method it takes a very long time for this method to return. I have not seen this same behavior with other JMS vendors. Any idea why this is happening?

Andreas Mueller

There is a bug report @ Javasoft for this with a workaround:

Bug ID 4344135