activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xavi <>
Subject Re: [Spam: 5.0] after some time running, Stomp client stops receiving new messages
Date Wed, 14 Mar 2007 17:50:17 GMT

you mean it's not possible to send keep alive commands from the Stomp client?
If it is, could you give me a hint about how to send these commands?

Thank you very much for your help.


James.Strachan wrote:
> On 3/14/07, xavi <> wrote:
>> Hello again,
>> it seems that we might have found the problem. The ISP where we have our
>> ActiveMQ server hosted tells us that they have some protection system
>> that
>> defines some inactivity timeouts at TCP session level. The timeout for
>> the
>> port that we are using is set to 15 minutes, and this matches with the
>> problems we are seeing (we stop receiving messages after 15 minutes of
>> inactivity).
>> People from the ISP suggest us to send some KeepAlives periodically. It
>> seems that ActiveMQ can be configured to send these KeepAlives
>> automatically, but we haven't found how to do it for Stomp connections.
>> We
>> tried this...
>> <transportConnector name="stomp"
>> uri="stomp://server:8000?transport.keepAlive=true"/>
>> and we've decreased the kernel's tcp KeepAlive time
>> (/proc/sys/net/ipv4/tcp_keepalive_time) to 60s, but the tcpdump doesn't
>> show
>> any keepalive packets, so we guess there's something wrong in what we are
>> doing, but... what?
>> On the other hand, is there a way to set the KeepAlive time (not only
>> enabling it or disabling it) at ActiveMQ's level?
> We've got support for keepalive & inactivity timeout in ActiveMQ
> already; we use it for OpenWire. The problem with enabling this is it
> would require the Stomp clients to send keep alive commands to keep
> the connection active.
> -- 
> James
> -------

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message