Re: SwiftMQ 7.4.1 + spring 2.5 + transactions + ReplyTo == trouble

We've found a bug - sorry! It comes up if you reply to temp queues by using pooled identified producers for these temp queues (via Spring's or SwiftMQ's caching, no matter) without really closing them (because the pool converts the close into a pool checkin) & if you use transacted sessions.

It only occurs if you use identified producers for the replies, that is, you create a producer per temp. queue. It does not occur if you use an unidentified producer (session.createProducer(null)). So I recommend to use an unidentified producer which is the recommended way for request/reply anyway (saves resources).