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

[IIT Software]

All objects expire <expirationtime> of non-use. You can see how effective you pooling is if you log via

-Dswiftmq.springsupport.debug=true

(if you have the chance for a change in future, remember to use an unidentified producer for all temp. queues)

Concerning the leak: It will disappear if you remove the receiveTimeout (which is unnecessary anyway) if you use the non-caching, non-pooling way.

[IIT Software]

This has been fixed.

[batalbot]

OK great.  7.5.1 doesn't seem to leak resources for normal queues or clustered queues.  I've tested it with and without caching in various ways so the problems seems solved.

Thanks for the fast turn-around.

[IIT Software]

Thanks for testing!