activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu Agarwal (JIRA)" <>
Subject [jira] [Commented] (AMQ-3402) Stomp over Websocket truncates the message body
Date Wed, 20 Jul 2011 13:05:58 GMT


Manu Agarwal commented on AMQ-3402:

Please find below a snippet from my cofig file(activemq.xml),

                <transportConnector name="openwire" uri="tcp://"/>
                <transportConnector name="stomp" uri="stomp://;transport.keepAliveResponseRequired=true"/>
                <transportConnector name="stomp+nio" uri="stomp+nio://;transport.keepAliveResponseRequired=true"/>
                <transportConnector name="websocket" uri="ws://"/>

My design is,

There is a websocket connection from my web page to the broker, which when the page is opened,
connects to the broker and sends a message to the queue using websockets.This is working fine.
On the other hand, there is a perl consumer listening on that queue.This is where the problem
arises.My perl consumer is not able to receive the message also, under webconsole, I didnt
see it subscribed to the queue, though I see a stomp connection under connections tab.

> Stomp over Websocket truncates the message body
> -----------------------------------------------
>                 Key: AMQ-3402
>                 URL:
>             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://"; 
> 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'},
>     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:


View raw message