activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ayhan Alkan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APLO-331) MQTT Websocket problem
Date Thu, 01 Aug 2013 11:15:51 GMT

     [ https://issues.apache.org/jira/browse/APLO-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ayhan Alkan updated APLO-331:
-----------------------------

    Priority: Blocker  (was: Major)
    
> MQTT Websocket problem
> ----------------------
>
>                 Key: APLO-331
>                 URL: https://issues.apache.org/jira/browse/APLO-331
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-mqtt
>    Affects Versions: 1.6, 1.7
>         Environment: OS: Ubuntu 12.04, JDK: 1.6.0_32, Clients: FF 22.0 Chrome 28.0.1500.71,
JS library: Paho MQTT JS Client (http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/)
>            Reporter: Ayhan Alkan
>            Priority: Blocker
>
> I get "AMQJS0016E Invalid MQTT message type 0." message while trying to connect MQTT
broker via ws probably due to  getting "\u0002\u0000\u0004"" stream.  The same script works
well with Active MQ 1.9.0-SNAPSHOT.  JS library stack trace is as follows:
> 0: "Client.startTrace"
> 1: "  "2013-07-21T06:01:48.018Z""
> 2: "  "0.0.0.0""
> 3: "Client.connect"
> 4: "  {"userName":"admin","password":"******","cleanSession":true,"keepAliveInterval":60}"
> 5: undefined
> 6: "  false"
> 7: "Client._socket_send"
> 8: "  {"type":1,"userName":"admin","password":"******","cleanSession":true,"keepAliveInterval":60,"clientId":"client123"}"
> 9: "Client._on_socket_message"
> 10: "  " \u0002\u0000\u0004""
> 11: "Client._on_socket_message"
> 12: "  {"type":0}"
> 13: "Client._disconnected"
> 14: "  16"
> 15: "  "AMQJS0016E Invalid MQTT message type 0.""
> 16: "Client.getTraceLog"
> 17: "  "2013-07-21T06:01:58.006Z""
> 18: "Client.getTraceLog in flight messages"
> 19: undefined

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message