Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Feb 26, 2018
Last activity: Mar 27, 2018
Posted: 26 Feb 2018 19:51 EST
Last activity: 27 Mar 2018 7:32 EDT
Closed

Tomcat sends HTTP 302 as a response to the F5 Health Monitor tool.

Hi Team,

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

PRPC :718

OS :Windows Server 2008 R2

***Edited by Moderator Marissa to update SR Details***

To see attachments, please log in.
System Administration
Support Case Exists

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice