Add a shutdown hook.
It doesn't sound like it has anything whatsoever to do with broker code.
On Oct 14, 2013, at 2:21 AM, HellKnight wrote:
> I typed "netstat -anp | grep 61616" in the server command window, and I find
> that "192.168.28.66 : 7042" is connected to server port 61616.
>
>
>
>
I typed "netstat -anp | grep 61616" in the server command window, and I find
that "192.168.28.66 : 7042" is connected to server port 61616.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/The-consumers-couldn-t-disconnect-from-broker-properly-tp4672722p4672724.html
Sent
Mr.Bish:
Thanks for helping me using ActiveMQ these days.
I turned off Inactivity monitor on the broker. I know it could kill old
stale connections after a given time. However, I think why there is "old
stale connections" in the first place is the real problem---If the client
program and the
On 10/14/2013 03:53 AM, HellKnight wrote:
The consumer program is writting in c# using NMS libraries and .NET 4.0,
running under windows 7/xp sp2.
The broker is running under redhat 6.3, ActiveMQ Version 5.8.0.
I am using virtual topic mode.
My problem is : Sometimes after the consumer has discon
The consumer program is writting in c# using NMS libraries and .NET 4.0,
running under windows 7/xp sp2.
The broker is running under redhat 6.3, ActiveMQ Version 5.8.0.
I am using virtual topic mode.
My problem is : Sometimes after the consumer has disconnected , I could
still find it active and c
