Fixing Common Problems
|Tcat Server reached its End of Life in 2017. Contact your Customer Success Manager to determine options for managing, monitoring, or deploying your application.|
If you are experiencing issues, review the following common problems and workarounds for Tcat Server.
When servers are registered, they are registered with a specific IP address. If you are testing on a laptop with a wireless connection and you move from one location to another, your IP address might change, and the servers no longer are able to communicate with Tcat Server.
APR Connector Failure using Tomcat 5.5 with Tcat
Errors such as "javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake" may result from limitations within the Tcat Server Administration Console, which cannot currently pair with SSL/TLS connectors under certain conditions.
Configure the Tomcat servers with an HTTP (non-SSL) connector on a port that the firewall blocks from the public internet, but not from the console.
Configure the Tomcat servers with an AJP (non-SSL) connector on a port that the firewall blocks from the public internet, but not from the console.