activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Regarding activemq sockets not getting closed
Date Tue, 09 Jun 2015 13:43:33 GMT
Can you put a breakpoint on the call to socket.close() in
TcpTransport.doStop() (
and see whether it's actually calling close() on the socket and also
whether it's succeeding?


On Mon, Jun 8, 2015 at 6:30 AM, tariq zafar <>

> I am having an issue with activemq broker. My requirement is that whenever
> the same client requests for a connection again then I should close the
> existing connection with that client and start a new one. For this purpose
> I
> have written a plugin that calls old connection closure getting the
> connection details that were saved in two maps earlier (for
> ConnectionContext and ConnectionInfo respectively) when that connection was
> created.
> I call these apis
> *
> ((TransportConnection)localConnectionContext.getConnection()).processRemoveConnection();
> //localConnectionContext is got from connContext save in map.
> ((TransportConnection)localConnectionContext.getConnection()).stop();
> *
> Using this code whenever I connect through another client with same client
> id in jconsole I can see remote address for the client getting changed and
> old remote address getting removed.
> However, my connection is getting closed only on activemq level and not on
> tcp level. Using netstat -a I can still see old connections that were made
> through same client in establishes state. I am using a websocket
> connection.
> What tcp setting should I do in activemq.xml that old sockets get closed on
> tcp level?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message