Idea ID: 2872380

More speaking Jersey Tracing Error

Status : New Idea

Hi all,

a customer of mine with NAM 5 faced this issue:

Some OAuth calls fails with the following error in Catalina.out:


<amLogEntry> 2021-12-16T11:11:54.839Z INFO NIDS OAuth  *Server responded with a response on thread https-jsse-nio-

3690 < 302

3690 < Found

3690 < X-Jersey-Tracing-000 : START       [ ---- /  ---- ms |  ---- %] baseUri=[https://lxxxxxxxxxxx/nidp/oauth/] requestUri=[https:/xxxxxxxxxxxxxx/nidp/oauth/nam/authz?response_type=code&clie



2021-12-16T11:11:54 org.apache.coyote.http11.Http11Processor service

SEVERE: Error processing request

org.apache.coyote.http11.HeadersTooLargeException: An attempt was made to write more data to the response headers than there was room available in the buffer. Increase maxHttpHeaderSize on the connector or write less data into the response headers.


I had them comment this  property in tomcat.conf:


JAVA_OPTS="${JAVA_OPTS} -Dcom.novell.nidp.oauth.jersey.trace=ALL"


And issue disappears.

What the customer notice about is that NAM replies with a generic error 500 printed on video that is not significant.

Only consulting the log they discovered the real cause.

They ask if its possible to have more speaking messages on video.