search cancel

Apache Tomcat Rejecting TLS Connection From Load Balancer

book

Article ID: 229929

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

After the upgrade to 15.9.3, Tomcat is rejecting connections from the load balancer.


SSO is turned off
App is listening on port 8043 where TLS is enabled
Direct connection to the app works fine but it fails while accessing the resource from the load balancer

The error in the APP system logs:

2021/12/01 07:31:03.870 | Dec 01, 2021 7:31:03 AM org.apache.tomcat.util.net.Nio2Endpoint$Nio2Acceptor failed
2021/12/01 07:31:03.886 | SEVERE: Socket accept failed
2021/12/01 07:31:03.886 | java.io.IOException: The specified network name is no longer available.

Resolution

After reaching out to the network team, it was found in one case that the Netscaler load balancer monitor was receiving HTTP 400 from Clarity Tomcat while using
full URL in a GET method.

The solution was to change from the full URL to a relative path as root dir "/ "