activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Shutdown hangs
Date Mon, 24 Jul 2006 15:32:42 GMT
Just to clear things up - is there a way that we should be changing
the configuration of the default TcpTransportServer so that it works
in your environment & to save you having a custom TcpTransportServer
implementation?

On 7/23/06, Kuppe <kuppe@360t.com> wrote:
>
> Found the problem. If the ServerSocket soTimeout is not set then the
> serverSocket.accept() will not return until the next accepted socket. In
> this case, when stop is called, it will wait until the run returns in the
> TcpTransportServer. If the soTimeout is not set, it wont stop!
>
> I extend the TcpTransportServer in order to implement my own socket
> negotiation process. I had removed the soTimeout setting:(
> --
> View this message in context: http://www.nabble.com/Shutdown-hangs-tf1934649.html#a5452283
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message