activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] [Commented] (APLO-325) Allow larger text messages on websocket connection
Date Thu, 25 Jul 2013 09:53:49 GMT


Hiram Chirino commented on APLO-325:

Hi Christian,

Thanks for the patches.. I've committed the tests and your patch to make the max WS message
size configurable.  I've also patched the JS client so that it breaks up big stomp frames
over multiple WS messages.

> Allow larger text messages on websocket connection
> --------------------------------------------------
>                 Key: APLO-325
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>          Components: apollo-stomp, apollo-web
>    Affects Versions: 1.6
>         Environment: Mac OS X 10.8.3, jdk 1.7.0_21
>            Reporter: Oliver Mross
>            Assignee: Christian Posta
>            Priority: Critical
>              Labels: features
>             Fix For: 1.7
>         Attachments: APLO-325-fix-attempt1.patch, APLO-325-reproduce-test_patch.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> I want to send 'not so large'  XML-content over a websocket connection to a server-side
middleware component, but the broker complains with the following message. If there is a way
to configure the text message size of the websocket connector within the broker config-file,
I've not found it. If not, please add an option to configure that within the config file or
in code in the case of an embedded broker.
>  org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameHandler textMessageTooLarge
> WARNING: Text message too large > 16384 chars for SCEP@2639a53a{l(/<->r(/,d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{WebSocketServletConnectionRFC6455
p=WebSocketParserRFC6455@60c5b6 state=DATA buffer= g=WebSocketGeneratorRFC6455@51542feb closed=false

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:

View raw message