activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3402) Stomp over Websocket truncates the message body
Date Tue, 19 Jul 2011 13:23:58 GMT

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

Manu Agarwal commented on AMQ-3402:
-----------------------------------

I tried with the latest snapshot, it installed and started properly this time, but I am not
able to get the consumers working. In the web-console under connections tab, I see connection
is there but no consumer on the queue. Also, message sent to that queue are not consumed by
the consumer.

Moreover, when a web socket sends a message to the queue, under web console that is being
shown as consumer on that queue. Please find below some snippets form log file,

2011-07-19 09:05:43,654 | INFO  | Connector vm://localhost Started | org.apache.activemq.broker.TransportConnector
| main
2011-07-19 09:05:43,776 | INFO  | Route: route1 started and consuming from: Endpoint[activemq://example.A]
| org.apache.camel.spring.SpringCamelContext | main
2011-07-19 09:05:43,802 | INFO  | Total 1 routes, of which 1 is started. | org.apache.camel.spring.SpringCamelContext
| main
2011-07-19 09:05:43,802 | INFO  | Apache Camel 2.7.0 (CamelContext: camel) started in 2.493
seconds | org.apache.camel.spring.SpringCamelContext | main
2011-07-19 09:05:46,271 | INFO  | Camel Console at http://0.0.0.0:8161/camel | org.eclipse.jetty.util.log
| main
2011-07-19 09:05:46,312 | INFO  | ActiveMQ Web Demos at http://0.0.0.0:8161/demo | org.eclipse.jetty.util.log
| main
2011-07-19 09:05:46,352 | INFO  | RESTful file access application at http://0.0.0.0:8161/fileserver
| org.eclipse.jetty.util.log | main
2011-07-19 09:05:46,358 | INFO  | Started SelectChannelConnector@0.0.0.0:8161 | org.eclipse.jetty.util.log
| main
2011-07-19 09:08:35,362 | WARN  | Broker localhost not started so using manu instead | org.apache.activemq.broker.BrokerRegistry
| qtp10838548-35
2011-07-19 09:08:42,337 | INFO  | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ NIO Worker
2011-07-19 09:09:21,683 | INFO  | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ NIO Worker
2011-07-19 09:09:58,544 | INFO  | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ NIO Worker
2011-07-19 09:12:07,792 | INFO  | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ NIO Worker
2011-07-19 09:16:15,944 | INFO  | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ NIO Worker

> Stomp over Websocket truncates the message body
> -----------------------------------------------
>
>                 Key: AMQ-3402
>                 URL: https://issues.apache.org/jira/browse/AMQ-3402
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.5.0
>         Environment: Ubuntu 10.1
>            Reporter: Manu Agarwal
>              Labels: Java, Script, Websocket
>
> I am using websocket for receiving messages over a queue using java script. This works
fine for smaller messages, but for large messages the message.body truncates the message and
also, JSON.parse(message.body) fails. 
> Is there a limit for the message size in Websockets. 
> I using java script (stomp.js) and trying to publish the messages on a web page. 
> Please find below the code snippet, 
> var url = "ws://manu.rsi.com:61614/stomp"; 
> var client = Stomp.client(url); 
> var tmp_destination = '/temp-queue/temp'; 
> function requestBlockInfo() { 
>     client.send('/queue/UI.Graph.Test.Q', {'reply-to': tmp_destination, 'command': 'blockinfo'},
"msg"); 
>     client.subscribe(tmp_destination,function(message) { 
>         alert(message.body); 
>         processMessage(JSON.parse(message.body)); 
>     }); 
> }; 
> onconnect = function(frame){ 
>         requestBlockInfo(); 
> }; 
> error_callback = function(error){ 
>     alert(error.headers.message); 
> }; 
>     
> var r = client.connect("", "" ,onconnect, error_callback); 
> When at the webpage, I received the message.body for message.body leangth greater then
60, it puts ... in between the message and truncates the message, so that its body length
is 60.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message