I got a similar exception with the proposed parameters.
BadMessageException: 500: Request header too largeĪt .HttpGenerator.generateRequest(HttpGenerator.java:259)Īt .http.HttpSenderOverHTTP$HeadersCallback.process(HttpSenderOverHTTP.java:203)Īt .IteratingCallback.processing(IteratingCallback.java:241)Īt .erate(IteratingCallback.java:224)Īt .(HttpSenderOverHTTP.java:58)Īt .nd(HttpSender.java:204)Īt .(HttpChannelOverHTTP.java:79)Īt .nd(HttpConnection.java:205)Īt .http.HttpConnectionOverHTTP$nd(HttpConnectionOverHTTP.java:202)Īt .(HttpConnectionOverHTTP.java:82)Īt .(HttpDestinationOverHTTP.java:37)Īt .(HttpDestinationOverHTTP.java:27)Īt .PoolingHttpDestination.process(PoolingHttpDestination.java:165)Īt .PoolingHttpDestination.process(PoolingHttpDestination.java:113)Īt .nd(PoolingHttpDestination.java:97)Īt .nd(HttpDestination.java:201)Īt .nd(HttpClient.java:538)Īt .nd(HttpRequest.java:694)Īt .nd(HttpRequest.java:678)Īt .ndProxyRequest(AbstractProxyServlet.java:539)Īt .rvice(ProxyServlet.java:88)Īt .(ProxyServlet.java:170)Īt .service(HttpServlet.java:790)Īt .ServletHolder.handle(ServletHolder.java:845)Īt .ServletHandler.doHandle(ServletHandler.java:583)Īt .(ContextHandler.java:1160)Īt .ServletHandler.doScope(ServletHandler.java:511)Īt .(ContextHandler.java:1092)Īt .(ScopedHandler.java:141)Īt .(ContextHandlerCollection.java:213)Īt .(HandlerCollection.java:119)Īt .(HandlerWrapper.java:134)Īt .Server.handle(Server.java:518)Īt .HttpChannel.handle(HttpChannel.java:308)Īt .HttpConnection.onFillable(HttpConnection.java:244)Īt .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)Īt .FillInterest.fillable(FillInterest.java:95)Īt .SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)Īt .(ExecuteProduceConsume.java:246)Īt .(ExecuteProduceConsume.java:156)Īt .(QueuedThreadPool.java:654)Īt .thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)Ĭaused by: Īt (Buffer.java:521)Īt (HeapByteBuffer.java:169)Īt .HttpGenerator.putSanitisedValue(HttpGenerator.java:985)Īt .HttpGenerator.putTo(HttpGenerator.java:1001)Īt .HttpGenerator.generateHeaders(HttpGenerator.java:718)Īt .HttpGenerator.generateRequest(HttpGenerator.java:233) INFO - Proxying /~rpc/getRevisionsListUpdate failed: null
The info log (Upsource-Logs\internal\services\bundleProcess\info.log) shows the following error: Looking at the Upsource Integration Tab in Youtrack shows: "HTTP 502 Bad Gateway Synchronized at 15:10" for one of the projects while the other projects continued to work just fine. Some time ago the Upsource Integration for one of our projects stopped working (vcs changes were no longer added to the tickets).
UPSOURCE YOUTRACK INTEGRATION WINDOWS
They are all running on the same Windows 2012 Server. I am using an external Hub (20), Youtrack (2017.3 Build 35234) and Upsource (20).
0 kommentar(er)
