activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Shannon <christopher.l.shan...@gmail.com>
Subject Re: Stomp over websocket connections timeout/hearbeat
Date Mon, 28 Sep 2015 16:38:40 GMT
I think you can also configure the heart beat in the connect frame of a
STOMP session by setting the heart-beat header.

https://stomp.github.io/stomp-specification-1.1.html#Heart-beating

On Mon, Sep 28, 2015 at 12:14 PM, Christopher Shannon <
christopher.l.shannon@gmail.com> wrote:

> Yes you can use heartbeats and it gets configured by using the inactivity
> monitor settings.  There was also a bug just fixed for it in 5.12.0:
> https://issues.apache.org/jira/browse/AMQ-5155
>
> To configure this on the server side you just need to set the inactivity
> monitor for the timeout period you want.
> http://activemq.apache.org/activemq-inactivitymonitor.html
>
> You client (such as stomp.js) is responsible for sending the heart beats
> periodically.
>
> On Mon, Sep 28, 2015 at 9:47 AM, aritz aguila <aritz.duir@gmail.com>
> wrote:
>
>> Hi,
>>
>> Im using stomp over websocket protocol... my actual broker configuration
>> is
>> very simple...
>>
>> <transportConnector name="ws" uri="ws://0.0.0.0:61614"/>
>>
>> I would like to use heartbeat parameter like in stomp configuration:
>>
>> stomp://0.0.0.0:0?transport.defaultHeartBeat=5000
>>
>> Or in openwire...
>>
>> <transportConnector name="openwire" uri="tcp://
>> 0.0.0.0:61616?wireFormat.maxInactivityDuration=30000/>
>>
>> But i cant find anything like this...
>>
>> Its possible configure the heartbeat in transportconnector for stomp over
>> websocket protocol?
>>
>> Thanks for all answers,
>>
>> Aritz.
>>
>>
>> --
>>
>> *P *
>>
>> *Antes de imprimir este email piense si es realmente necesario: el medio
>> ambiente es cosa de todos.*
>>
>> *Before printing this email, think whether it is really necessary:
>> environment is a matter of all.*
>>
>
>

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