OneClick Server is not loading - giving "HTTP Status 400 – "Request header is too large"
search cancel

OneClick Server is not loading - giving "HTTP Status 400 – "Request header is too large"


Article ID: 248086


Updated On:


CA Spectrum DX NetOps


The secondary One-Click server failed to load and after attempting to restart both webtomcat and tomcat, as well as a server reboot, we are now seeing the following:


HTTP Status 400 – Bad Request

Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).


java.lang.IllegalArgumentException: Request header is too large	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(	org.apache.coyote.http11.Http11Processor.service(	org.apache.coyote.AbstractProcessorLight.process(	org.apache.coyote.AbstractProtocol$ConnectionHandler.process($SocketProcessor.doRun(	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(	org.apache.tomcat.util.threads.ThreadPoolExecutor$	org.apache.tomcat.util.threads.TaskThread$

Note The full stack trace of the root cause is available in the server logs.


Release : 21.2

Component :


The maxHttpHeaderSize needed to be increased in the server.xml file.


The solution is to increase the http header size in OneClick by doing the following on the OneClick server: Create a backup of the $SPECROOT/tomcat/conf/server.xml file Edit the $SPECROOT/tomcat/conf/server.xml file Find the maxHttpHeaderSize="8192" parameter Change to maxHttpHeaderSize="16384" Save the change Restart Spectrum tomcat