Apache Tomcat Common Log Errors and their Meanings

Apache: (http-errs)

mod_jk child init 1 0 – harmless, disregard

Generally, these next 4 errors occur when a user stops loading a page:

Error ajp_process_callback – write failed – The remote browser client aborted the HTTP request – can

happen when Tomcat is overloaded and request latency increases significantly – user breaks browser connection

while downloading data – error #1 in set

ajp13.service() ajpGetReply recoverable error 3 – harmless ajp error? Comes with above error – error #2

in set

ajp13.service() Error forwarding ajp13:<server:port> 1 0 – another harmless ajp error? error #3 in set

mod_jk.handler() Error connecting to tomcat 3 – The Tomcat AjpConnector socket isn’t open; also, error

#4 in set – these 4 errors occur when a user hits "Stop" in his browser

child process xxxxx still did not exit, sending a SIGKILL –

Tomcat: (catalina.out)

Broken Pipe – something closed the socket on the backend (not the server) – user interrupted loading –

generally harmless

INFO: RESET –

INFO: server has been restarted or reset this connection – occurs whenever read() is attempted on the socket

InputStream when Apache is being restarted – Apache restarts itself after a given # of requests to free its

memory (to avoid memory leaks on some OSs) – this message is NORMAL with Apache

ca.edbc.util.EdbcEx – A request was made on a closed connection. –

ca.edbc.util.EdbcEx – A new request may not be started while a request is still active. –

EDBC: (errlog.log)

E_CL2660_CI_LICENSE_ERR Computer Associates Licensing Error – disregard?

E_GC220B_EXP_RCV_FAIL GCA expedited receive failure: reason follows. – System dependant problem? Try another

protocol?

E_CLFE07_BS_READ_ERR Read from peer process failed; it may have exited. – occurs when a client exits

unexpectedly; harmless – no way to turn them off. If this error is with others about communications problems,

it is like the UNIX "connection reset by peer" message – check if clients are connected via a NAT firewall on

their side or yours. If so, the idle timeout value for the firewall will need to be adjusted

E_GC2809_NTWK_CONNECTION_FAIL Network connection failed for protocol TCP_IP, to node 10.70.132.132, port 134;

status follows. (followed by) E_CLFE05_BS_CONNECT_ERR Unable to make outgoing connection. and System

communication error: Transport endpoint is not connected. – network problems – may need to restart EDBC, but

often happens during a backup – those messages can be disregarded.

E_GC2210_LCL_ABORT Session failure: Local ABORT condition. – EDBC has failed and needs to be restarted. The SIS

tomcat needs to be restarted as well.

System communication error: Connection reset by peer. – usually means ISIS/"The IBM"/"IDMS"/Whatever it’s

called has failed and both EDBC and the SIS tomcat need to be restarted.