You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Christian Posta (JIRA)" <ji...@apache.org> on 2013/07/09 17:47:55 UTC

[jira] [Assigned] (APLO-325) Allow larger text messages on websocket connection

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

Christian Posta reassigned APLO-325:
------------------------------------

    Assignee: Christian Posta
    
> Allow larger text messages on websocket connection
> --------------------------------------------------
>
>                 Key: APLO-325
>                 URL: https://issues.apache.org/jira/browse/APLO-325
>             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
>
>   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(/127.0.0.1:51180)<->r(/127.0.0.1:8082),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 buffer=-1}

--
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