[
https://issues.apache.org/jira/browse/KNOX-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep More updated KNOX-836:
------------------------------
Status: Patch Available (was: Open)
For the inbound connections (data streaming in from the backend service) make
the message size MAX (hardcoded). Max message size (from configs) can still be
set using the existing properties (gateway.websocket.max.text.size)
> Websockets connection is terminated when message size is larger than 65536
> --------------------------------------------------------------------------
>
> Key: KNOX-836
> URL: https://issues.apache.org/jira/browse/KNOX-836
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Sandeep More
> Assignee: Sandeep More
> Attachments: KNOX-836.001.patch
>
>
> In some cases, or e.g. in Zeppelin with large demo Notebooks, Knox will
> abruptly close connection with error:
> [exec] org.eclipse.jetty.websocket.api.MessageTooLargeException: Text message
> size [1313822] exceeds maximum size [65536]
> [exec] at
> org.eclipse.jetty.websocket.api.WebSocketPolicy.assertValidTextMessageSize(WebSocketPolicy.java:140)
> [exec] at
> org.eclipse.jetty.websocket.common.Parser.assertSanePayloadLength(Parser.java:127)
> [exec] at
> org.eclipse.jetty.websocket.common.Parser.parseFrame(Parser.java:482)
> [exec] at
> org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:254)
> [exec] at
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:632)
> [exec] at
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:480)
> [exec] at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
> [exec] at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> [exec] at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> [exec] at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
