Last activity: 27 Mar 2018 7:32 EDT
Tomcat sends HTTP 302 as a response to the F5 Health Monitor tool.
Tomcat (reviewed from the access logs) sends responses to F5 Health Monitor tool as HTTP 302 and we are assuming that this might be causing abrupt logoff issues for the PEGA application for the end user @Production environment.
The below mentioned errors has been observed in the Tomcat system error logs.
Feb 25, 2018 3:32:25 AM com.hazelcast.nio.tcp.TcpIpConnection
INFO: [xx.xx.xx.xx]:5705 [65b6da5135c3ecccb0f77ce104466df8] [3.4.1] Connection [xx.corp.agp.ads/xx.xx.xx.xx:50656] lost. Reason: java.io.EOFException[Remote socket closed!]
Msg: Timeout waiting for connection
log4j:ERROR Cause: com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection
log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
log4j:ERROR Msg: Transport error: 302 Error: Found
log4j:ERROR Cause: null
Environment details below :
Tomcat : 7.0.57
OS :Windows Server 2008 R2
***Edited by Moderator Marissa to update SR Details***