Arjan van den Berg created AMQ-5155:
---------------------------------------
Summary: 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
Reporter: Arjan van den Berg
Priority: Minor
>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.2#6252)
