I am very new to using Upsource, and I have recently set up an instance, and have been getting the following error message (below).  I am unsure of what I can do to configure my system to get around this issue (if there is a way), and am just looking for some guidance and a point in the right direction from others who are more experienced.  Thanks for any help that anyone may be able to provide.


[2016-03-24 14:26:09,046] [Upsource Error] org.eclipse.jetty.websocket.api.MessageTooLargeException: Text message size [40286089] exceeds maximum size [20971520]
[2016-03-24 14:26:09,047] [Upsource Error] at org.eclipse.jetty.websocket.api.WebSocketPolicy.assertValidTextMessageSize(
[2016-03-24 14:26:09,047] [Upsource Error] at org.eclipse.jetty.websocket.common.Parser.assertSanePayloadLength(
[2016-03-24 14:26:09,047] [Upsource Error] at org.eclipse.jetty.websocket.common.Parser.parseFrame(
[2016-03-24 14:26:09,047] [Upsource Error] at org.eclipse.jetty.websocket.common.Parser.parse(
[2016-03-24 14:26:09,047] [Upsource Error] at
[2016-03-24 14:26:09,047] [Upsource Error] at
[2016-03-24 14:26:09,047] [Upsource Error] at$
[2016-03-24 14:26:09,048] [Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
[2016-03-24 14:26:09,048] [Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool$
[2016-03-24 14:26:09,048] [Upsource Error] at



Comment actions Permalink

Hi Ryan,

Thank you for posting the request.

The piece of the log shows that websocket limit was exceeded. What we need to find is the root cause of this behavior.

Let's start from logs folder from Upsource installation directory. When you have a chance please send it to

Thanks in advance.  


Comment actions Permalink

Thank you for the response.  I will send over the log folder soon

Comment actions Permalink


have you found a cause for the problem?
I'm getting the same Exception.

Maybe fixed with Upsource 3?
Because I'll plan to update soon.


Comment actions Permalink

Hello Christof,


I have not heard back about what the issue is, but they have created an issue and it is being investigated.  The issue can be seen here if you are interested in following it:




Please sign in to leave a comment.