Interesting. I just re-read your question and noticed this which makes me think it is a configuration on the broker or network settings in K8s
It basically loops like this all day long and I can’t figure out why. When I run this locally on my development machine the connection remains open and and not closing on its own****.
@Aaron @TomF - any ideas here?
Just a guess from me, but can you check the client-profile and the JMS JNDI Connection Factory settings for keepalives and see if there is anything disabled or drastically different than what you have locally?
As defaults I see this in my local docker but your admin may change some of these things based on what they expect to see or network restrictions in your k8s cluster.
On the client-profile
On the JMS Connection Factory
