every two minutes is quite a long time. the default inactivity monitor on the tcp transport will timeout after 30s (although i think you'd see something in the logs if that was the reason the socket was closed). the default inactivity monitor also sends heart beat messages so that the connection doesn't get shutdown due to user inactivity. there must be something else going on in your situation
On Wed, Dec 19, 2012 at 10:51 AM, ruiluis <rui.l...@eyesee.pt> wrote: > its driving me crazy because it cannot be due to inactivity because i > ensure > that it sends something almost every two minutes.. some third process > removing the connections that is very strange because the server is a clean > server running almost nothing.. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660921.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
