Re: Proper life cycle management with springsupport.jar

The resource limits are checked at the router side anyway, not at the client. So these infos are not passed to the client and thus not available there.

The Springsupport was actually created to get over the limitations of Spring's JmsTemplate which creates a new connection, session, producer (and closes it) for each message sent over this template.

As I mentioned already, we do not block an application by putting it on hold while it waits on a pooled resource. Therefore you should limit the number of app threads using springsupport in the app itself.