OC Tomcat Broken pipe errors leading to HTTP 500 Internal Server Errors
search cancel

OC Tomcat Broken pipe errors leading to HTTP 500 Internal Server Errors

book

Article ID: 369567

calendar_today

Updated On:

Products

DX NetOps CA Spectrum

Issue/Introduction

The OneClick client is slow.  Usually it is normal and responds quickly but it has started to slow down.  There are broken pipe errors in the tomcat log which lead to HTTP 500 Internal Server Errors:

$SPECROOT/tomcat/logs

std.out (Windows)

catalina.out (Linux)


Jun 09, 2024 11:01:54 PM (https-jsse-nio-8443-exec-27) (org.apache.cxf.jaxrs.provider.AbstractJAXBProvider) - (WARN) - javax.xml.bind.MarshalException
 - with linked exception:
[javax.xml.stream.XMLStreamException: org.codehaus.jettison.json.JSONException: java.io.IOException: Broken pipe]

Jun 09, 2024 11:01:54 PM (https-jsse-nio-8443-exec-27) (org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper) - (WARN) - javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error

Cause

Network issues

Resolution

Stop the Spectrum Tomcat service/process and remove the tomcat/work folder which is used for the Tomcat cache:

systemctl stop processd

Delete the $SPECROOT/tomcat/work folder

systemctl start processd

 

On Windows, stop the Spectrum Process Daemon.

Delete the $SPECROOT/tomcat/work folder

Start the Spectrum Process Daemon.