activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francisco Javier Benito Gómez (JIRA) <>
Subject [jira] [Created] (AMQ-5044) Stomp Websocket - Multiple Frames is not working
Date Wed, 12 Feb 2014 09:53:19 GMT
Francisco Javier Benito Gómez created AMQ-5044:

             Summary: Stomp Websocket - Multiple Frames is not working
                 Key: AMQ-5044
             Project: ActiveMQ
          Issue Type: Bug
          Components: stomp
    Affects Versions: 5.9.0
            Reporter: Francisco Javier Benito Gómez

When you send a message through Stomp Websocket using stomp.js, if you try to send a message
bigger than 16kb, stomp.js splits the message in multiple frames. ActiveMQ is not able to
manage this kind of message.

The showed error is:
org.apache.activemq.transport.stomp.ProtocolException: The maximum command length was exceeded
	at org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(
	at org.apache.activemq.transport.stomp.StompWireFormat.readLine(
	at org.apache.activemq.transport.stomp.StompWireFormat.parseAction(
	at org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(
	at org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(
	at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameHandler.onFrame(
	at org.eclipse.jetty.websocket.WebSocketParserRFC6455.parseNext(
	at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455.handle(
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
	at org.eclipse.jetty.util.thread.QueuedThreadPool$

The second framed is processed as a new message, so it is trying to process the body as a
command part. 

This message was sent by Atlassian JIRA

View raw message