Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Stack Overflow by Factor Three
, 1 year ago
Text message size [130353] exceeds maximum size [65536]
via knox-dev by ASF subversion and git services (JIRA), 9 months ago
via knox-dev by Sumit Gupta (JIRA), 9 months ago
via knox-dev by Sumit Gupta (JIRA), 9 months ago
via knox-dev by Sandeep More (JIRA), 9 months ago
via GitHub by mrwhy-orig
, 1 year ago
Text message size [103168] exceeds maximum size [65536]
org.eclipse.jetty.websocket.api.MessageTooLargeException: Text message size [130353] exceeds maximum size [65536]	at org.eclipse.jetty.websocket.api.WebSocketPolicy.assertValidTextMessageSize(WebSocketPolicy.java:140)	at org.eclipse.jetty.websocket.common.Parser.assertSanePayloadLength(Parser.java:127)	at org.eclipse.jetty.websocket.common.Parser.parseFrame(Parser.java:482)	at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:254)	at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:632)	at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:480)	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)	at java.lang.Thread.run(Thread.java:745)