You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arjan van den Berg (JIRA)" <ji...@apache.org> on 2010/10/12 09:52:41 UTC
[jira] Created: (AMQ-2972) STOMP over Websockets do not work in
Chrome
STOMP over Websockets do not work in Chrome
-------------------------------------------
Key: AMQ-2972
URL: https://issues.apache.org/activemq/browse/AMQ-2972
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.4.1
Environment: Windows XP, Chrome 6.0.472.63
Reporter: Arjan van den Berg
The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
( http://activemq.apache.org/websockets.html ).
On the ActiveMQ side, the following error appears:
INFO | Started SelectChannelConnector@0.0.0.0:8161
ERROR | handle failed?
java.lang.IllegalArgumentException: !utf8
at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2972) STOMP over Websockets do not work in
Chrome
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2972.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.5.0
Assignee: Dejan Bosanac
fixed with svn revision 1022029. Thanks for digging this out.
> STOMP over Websockets do not work in Chrome
> -------------------------------------------
>
> Key: AMQ-2972
> URL: https://issues.apache.org/activemq/browse/AMQ-2972
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows XP, Chrome 6.0.472.63
> Reporter: Arjan van den Berg
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
>
> The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
> ( http://activemq.apache.org/websockets.html ).
> On the ActiveMQ side, the following error appears:
> INFO | Started SelectChannelConnector@0.0.0.0:8161
> ERROR | handle failed?
> java.lang.IllegalArgumentException: !utf8
> at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
> at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
> at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
> at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
> at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (AMQ-2972) STOMP over Websockets do
not work in Chrome
Posted by "Arjan van den Berg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62517#action_62517 ]
Arjan van den Berg edited comment on AMQ-2972 at 10/12/10 4:58 AM:
-------------------------------------------------------------------
I've managed to solve the issue by upgrading the jetty components to version 7.1.6
So, in lib/web, I updated jetty-all-server-7.0.1.v20091125.jar to jetty-all-server-7.1.6.v20100715.jar
and jetty-websocket-7.0.1.v20091125.jar to jetty-websocket-7.1.6.v20100715.jar.
Probably the websocket specification has changed between jetty releases.
Also, some extra documentation on how to use the client libraries specifically for ActiveMQ would be handy.
It took some time for me to find out that the destination should be in the form "/topic/test.topic" or "/queue/test.queue".
was (Author: bergamot):
I've managed to solve the issue by upgrading the jetty components to version 7.1.6
So, in lib/web, I updated jetty-all-server-7.0.1.v20091125.jar to jetty-all-server-7.1.6.v20100715.jar
and jetty-websocket-7.0.1.v20091125.jar to jetty-websocket-7.1.6.v20100715.jar.
Also, some extra documentation on how to use the client libraries specifically for ActiveMQ would be handy.
It took some time for me to find out that the destination should be in the form "/topic/test.topic" or "/queue/test.queue".
> STOMP over Websockets do not work in Chrome
> -------------------------------------------
>
> Key: AMQ-2972
> URL: https://issues.apache.org/activemq/browse/AMQ-2972
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows XP, Chrome 6.0.472.63
> Reporter: Arjan van den Berg
>
> The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
> ( http://activemq.apache.org/websockets.html ).
> On the ActiveMQ side, the following error appears:
> INFO | Started SelectChannelConnector@0.0.0.0:8161
> ERROR | handle failed?
> java.lang.IllegalArgumentException: !utf8
> at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
> at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
> at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
> at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
> at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2972) STOMP over Websockets do not work in
Chrome
Posted by "Arjan van den Berg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62517#action_62517 ]
Arjan van den Berg commented on AMQ-2972:
-----------------------------------------
I've managed to solve the issue by upgrading the jetty components to version 7.1.6
So, in lib/web, I updated jetty-all-server-7.0.1.v20091125.jar to jetty-all-server-7.1.6.v20100715.jar
and jetty-websocket-7.0.1.v20091125.jar to jetty-websocket-7.1.6.v20100715.jar.
Also, some extra documentation on how to use the client libraries specifically for ActiveMQ would be handy.
It took some time for me to find out that the destination should be in the form "/topic/test.topic" or "/queue/test.queue".
> STOMP over Websockets do not work in Chrome
> -------------------------------------------
>
> Key: AMQ-2972
> URL: https://issues.apache.org/activemq/browse/AMQ-2972
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows XP, Chrome 6.0.472.63
> Reporter: Arjan van den Berg
>
> The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
> ( http://activemq.apache.org/websockets.html ).
> On the ActiveMQ side, the following error appears:
> INFO | Started SelectChannelConnector@0.0.0.0:8161
> ERROR | handle failed?
> java.lang.IllegalArgumentException: !utf8
> at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
> at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
> at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
> at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
> at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2972) STOMP over Websockets do not work in
Chrome
Posted by "Arjan van den Berg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62638#action_62638 ]
Arjan van den Berg commented on AMQ-2972:
-----------------------------------------
The jetty-all-server jar is an aggregate jar that contains org.eclipse.jetty.security.HashLoginService. Maybe your classpath is non-standard or there's a difference between ActiveMQ 5.4.1 and Fuse 5.4.0?
> STOMP over Websockets do not work in Chrome
> -------------------------------------------
>
> Key: AMQ-2972
> URL: https://issues.apache.org/activemq/browse/AMQ-2972
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows XP, Chrome 6.0.472.63
> Reporter: Arjan van den Berg
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
>
> The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
> ( http://activemq.apache.org/websockets.html ).
> On the ActiveMQ side, the following error appears:
> INFO | Started SelectChannelConnector@0.0.0.0:8161
> ERROR | handle failed?
> java.lang.IllegalArgumentException: !utf8
> at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
> at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
> at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
> at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
> at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2972) STOMP over Websockets do not work in
Chrome
Posted by "Julian Cable (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62625#action_62625 ]
Julian Cable commented on AMQ-2972:
-----------------------------------
Using apache-activemq-5.4.0-fuse-00-00
I tried updating the jetty jars and got:
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to load type: org.eclipse.jetty.security.HashLoginService. Reason: java.lang.ClassNotFoundException: org.eclipse.jetty.security.HashLoginService; nested exception is java.lang.ClassNotFoundException: org.eclipse.jetty.security.HashLoginService
I tried adding jetty-security-7.1.6.v20100715.jar but that didn't help.
> STOMP over Websockets do not work in Chrome
> -------------------------------------------
>
> Key: AMQ-2972
> URL: https://issues.apache.org/activemq/browse/AMQ-2972
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.4.1
> Environment: Windows XP, Chrome 6.0.472.63
> Reporter: Arjan van den Berg
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
>
> The STOMP over Websocket support does not work with both client libraries referenced from the ActiveMQ Websockets page
> ( http://activemq.apache.org/websockets.html ).
> On the ActiveMQ side, the following error appears:
> INFO | Started SelectChannelConnector@0.0.0.0:8161
> ERROR | handle failed?
> java.lang.IllegalArgumentException: !utf8
> at org.eclipse.jetty.util.Utf8StringBuilder.append(Utf8StringBuilder.java:112)
> at org.eclipse.jetty.websocket.WebSocketParser.parseNext(WebSocketParser.java:147)
> at org.eclipse.jetty.websocket.WebSocketConnection.handle(WebSocketConnection.java:75)
> at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:252)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
> at java.lang.Thread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.