Charlie Mordant created AMQ-5169:
------------------------------------
Summary: CLONE - heart-beat is disabled when connecting to web
socket
Key: AMQ-5169
URL: https://issues.apache.org/jira/browse/AMQ-5169
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: Google Chrome 29.0.1547.76 (Official Build 223446)
Reporter: Charlie Mordant
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)
