Looks like you were able to track down and fix this: https://issues.apache.org/jira/browse/KNOX-1828
Kevin Risden On Sat, Mar 16, 2019 at 5:12 PM Shawn Weeks <[email protected]> wrote: > Working on an HDP 3.1.0 Cluster Knox 1.0 and I'm running into an issue > with Zeppelin and WebSocket's not working. I've increased all of the Knox > parameters I can think of and after looking through the code I can't find > anything that's actually set to 65536 unless I go over and look in Jetty's > sources. Is there another parameter in Knox that handles this or a > different way to do this with the new topology deployments. I've looked > through the code and KNOX-836 changes are there and all the defaults are > set to integer max. > > 2019-03-16 15:26:29,328 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] > > gateway.websocket.max.binary.buffer.size=1048576 > gateway.websocket.max.binary.size=1048576 > gateway.websocket.max.text.buffer.size=1048576 > gateway.websocket.max.text.size=1048576 > gateway.websocket.input.buffer.size=1048576 > > Thanks > Shawn Weeks >
