You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jeff Mesnil (JIRA)" <ji...@apache.org> on 2014/06/11 16:21:02 UTC
[jira] [Comment Edited] (AMQ-4740) heart-beat is disabled when
connecting to web socket
[ https://issues.apache.org/jira/browse/AMQ-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027792#comment-14027792 ]
Jeff Mesnil edited comment on AMQ-4740 at 6/11/14 2:19 PM:
-----------------------------------------------------------
Issue is still happening with ActiveMQ 5.10.0.
In the log:
2014-06-11 15:27:59,776 | WARN | Transport Connection to: StompSocket_1430955985 failed: java.io.IOException | org.apache.activemq.broker.TransportConnection.Transport | qtp542980314-29
The corresponding STOMP frames were:
CONNECT
accept-version:1.1,1.0
heart-beat:20000,60000
CONNECTED
server:ActiveMQ/5.10.0
heart-beat:60000,20000
session:ID:jeff.local-51540-1402496252734-2:1
version:1.1
And the Web Socket client was sending PING frames every 20 seconds.
was (Author: jmesnil):
Issue is still happening with ActiveMQ 5.10.0.
> heart-beat is disabled when connecting to web socket
> ----------------------------------------------------
>
> Key: AMQ-4740
> URL: https://issues.apache.org/jira/browse/AMQ-4740
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.8.0, 5.10.0
> Environment: Google Chrome 29.0.1547.76 (Official Build 223446)
> Reporter: Jeff Mesnil
> Fix For: 5.9.1, 5.10.0
>
> Attachments: AMQ-4740.patch
>
>
> If I use the stomp.js library to connect to ActiveMQ over its WebSocket url (ws://localhost:61614), the CONNECTED frame returns with disabled heart-beat:
> CONNECTED
> heart-beat:0,0
> session:ID:retsina.local-63633-1380117269290-2:1
> server:ActiveMQ/5.8.0
> version:1.1
> If I connect to its TCP socket (localhost:61613), the CONNECT frame will have heart-beat:
> CONNECTED
> heart-beat:10000,10000
> session:ID:retsina.local-63384-1380115729700-2:12
> server:ActiveMQ/5.8.0
> version:1.1
> In both case, the stomp.js send the same CONNECT frame with heart-beat:
> CONNECT
> login:user
> passcode:password
> accept-version:1.1,1.0
> heart-beat:10000,10000
> Is heart-beat disabled on purpose for Web Socket? Please note that the stomp.js does support heart-beat (using window.setInterval in a Web browser)
--
This message was sent by Atlassian JIRA
(v6.2#6252)