activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Kelly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4740) heart-beat is disabled when connecting to web socket
Date Sun, 25 May 2014 18:16:02 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008393#comment-14008393
] 

Chad Kelly commented on AMQ-4740:
---------------------------------

Please reopen this ticket. The bug described above is still present in 5.9.1. I tried both
cases, heartbeat set to  0,0 and 10000,10000. Slightly different buggy behaviors, but it still
does not work. Please:
1) download 5.9.1
2) bin/activemq console xbean:examples/conf/activemq-demo.xml
3) open two browsers (firefox/chrome) to http://localhost:8161/demo/websocket/index.html
4) type a few messages over a 5 minute period

 WARN | Transport Connection to: StompSocket_1998606381 failed: java.io.IOException
 WARN | Transport Connection to: StompSocket_178709817 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:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
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:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)


> 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)

Mime
View raw message