Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6326A10F2F for ; Thu, 3 Apr 2014 13:28:25 +0000 (UTC) Received: (qmail 55108 invoked by uid 500); 3 Apr 2014 13:28:23 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 54660 invoked by uid 500); 3 Apr 2014 13:28:18 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 54422 invoked by uid 99); 3 Apr 2014 13:28:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 13:28:15 +0000 Date: Thu, 3 Apr 2014 13:28:15 +0000 (UTC) From: "John Prillaman (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AMQ-4740) heart-beat is disabled when connecting to web socket MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958800#comment-13958800 ] John Prillaman edited comment on AMQ-4740 at 4/3/14 1:27 PM: ------------------------------------------------------------- I have applied this patch to version 5.9.0 and have also installed a 5.10.0 snapshot. With each version I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. ---------- stomp.js output connected to server ActiveMQ/5.10-SNAPSHOT controller.js:20 send PING every 10000ms controller.js:20 check PONG every 10000ms controller.js:20 <<< PONG controller.js:20 >>> PING controller.js:20 did not receive server activity for the last 20005ms controller.js:20 Whoops! Lost connection to ws://172.16.99.73:61614/stomp controller.js:20 function () { [native code] } stomp.js:238 --------------------- active mq console WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread "ActiveMQ InactivityMonitor Worker" java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread "ActiveMQ InactivityMonitor Worker" java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) was (Author: jprillaman): I have applied this patch to version 5.9.0 and have also installed a 5.10.0 snapshot. With each version I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread "ActiveMQ InactivityMonitor Worker" java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) > 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 > 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)