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 32EAD17C7F for ; Thu, 2 Apr 2015 07:13:55 +0000 (UTC) Received: (qmail 61717 invoked by uid 500); 2 Apr 2015 07:13:54 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 61655 invoked by uid 500); 2 Apr 2015 07:13:54 -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 61643 invoked by uid 99); 2 Apr 2015 07:13:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2015 07:13:54 +0000 Date: Thu, 2 Apr 2015 07:13:54 +0000 (UTC) From: "Peter Pfort (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets 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-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392271#comment-14392271 ] Peter Pfort commented on AMQ-5155: ---------------------------------- Hi Timothy, your change in version 5.12 isn't complete. You forget the "else" before the "onStompCommand ...", like in the snippet from Claudio. The "(StompFrame)wireFormat.unmarshal" throw an EOFException, because the KeepAlive command isn't handled in it. Then the session is marked as failed. Please complete the code. Peter > Heartbeat fails in STOMP over WebSockets > ---------------------------------------- > > Key: AMQ-5155 > URL: https://issues.apache.org/jira/browse/AMQ-5155 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.9.1, 5.10.0 > Reporter: Arjan van den Berg > Assignee: Timothy Bish > Priority: Minor > Fix For: 5.12.0 > > Attachments: AMQ-5155-jetty8.diff, AMQ-5155-jetty9.diff > > > From AMQ-4740: > 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 > heart-beat:10000,10000 > session:ID:localhost.localdomain-45596-1396530920609-2:2 > server:ActiveMQ/5.10-SNAPSHOT > version:1.1 > send PING every 10000ms > check PONG every 10000ms > <<< PONG > >>> PING > did not receive server activity for the last 20005ms > Whoops! Lost connection to ws://172.16.99.73:61614/stomp > --------------------- activemq 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) > For me it looks as if the StompInactivityMonitor is delivering its events to the wrong Transport, i.e. it needs a "narrow()" when setting it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)