[jira] [Commented] (KNOX-1828) Websocket Parameters Not Being Applied

["Shawn Weeks (JIRA)" <ji...@apache.org>]

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

Shawn Weeks commented on KNOX-1828:
-----------------------------------

So the issues seems to be that the WebSocketContainer being created in ProxyWebSocketAdapter isn't inheriting the max binary and max text message sizes from frontEndSession. Not really sure how it's supposed to work but the policy should be getting copied over and isn't.

> Websocket Parameters Not Being Applied
> --------------------------------------
>
>                 Key: KNOX-1828
>                 URL: https://issues.apache.org/jira/browse/KNOX-1828
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Shawn Weeks
>            Priority: Minor
>
> It looks like the gateway.websocket parameters are not making it back to Jetty. Knox set's this parameter to Integer.MAX_VALUE and setting the parameters like the following have no effect.
> {code:java}
> <property>
> <name>gateway.websocket.input.buffer.size</name>
> <value>1048576</value>
> </property>
> <property>
> <name>gateway.websocket.max.binary.buffer.size</name>
> <value>1048576</value>
> </property>
> <property>
> <name>gateway.websocket.max.binary.size</name>
> <value>1048576</value>
> </property>
> <property>
> <name>gateway.websocket.max.text.buffer.size</name>
> <value>1048576</value>
> </property>
> <property>
> <name>gateway.websocket.max.text.size</name>
> <value>1048576</value>
> </property>
> {code}
>  
>  
> {code:java}
> 2019-03-16 16:11:43,548 ERROR gateway.websockets (ProxyWebSocketAdapter.java:cleanupOnError(171)) - Error: org.eclipse.jetty.websocket.api.MessageTooLargeException: Resulting message size [73,728] is too large for configured max of [65,536]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)