[KNOX-1828] Websocket Parameters Not Being Applied

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.1.0, 1.2.0
• Fix Version/s: 1.3.0
• Assignee: Shawn Weeks
• Reporter: Shawn Weeks
• Created: 16/Mar/19 21:36
• Updated: 21/Oct/19 14:23
• Resolved: 19/Mar/19 15:34

Description

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.

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

 

 

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]

 

Issue Links

• relates to: KNOX-836 Websockets connection is terminated when message size is larger than 65536
• relates to: KNOX-752 Knox Websocket support
• links to: GitHub Pull Request #75