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

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

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).

Exception

java.lang.IllegalArgumentException: Request header is too large	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:614)	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294)	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)	java.lang.Thread.run(Thread.java:750)

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

Environment

Release : 21.2

Component :

Cause

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

Resolution

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