Shawn Weeks created KNOX-1828:
---------------------------------
Summary: 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
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)
