Bug 62519

Summary: Getting 500 error code in AJP logs intermediately
Product: Apache httpd-2 Reporter: sasikishore.k
Component: CoreAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: NEEDINFO ---    
Severity: major    
Priority: P2    
Version: 2.4.25   
Target Milestone: ---   
Hardware: PC   
OS: Linux   

Description sasikishore.k 2018-07-03 10:26:01 UTC
Hi,

We are using Apache HTTP server version 2.2.25 and 2.2.23. 
But the server is returning 500 error code in AJP logs and the request is not reached tomcat access logs, but tomcat also not busy.

As per AGP log, noticed four or five requests failing with error code 500 once in a day. This is causing, showing the status of our application disconnected.  

We modified below configuration for AJP connecter, but there is no change in behavior.

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address="localhost"  enableLookups="true" maxThreads="500" connectionTimeout="120000" URIEncoding="UTF-8" />

With

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address="127.0.0.1" enableLookups="false" maxThreads="500" connectionTimeout="120000" URIEncoding="UTF-8" /> 


Can you please do the needful to resolve this issue. 

Thanks,
Sasi
Comment 1 Eric Covener 2018-07-03 10:49:26 UTC
> Can you please do the needful to resolve this issue. 

2.2 has been retired and bugzilla is for reporting bugs, not for support. If you have an observation from your error logs, I suggest users@httpd.apache.org
Comment 2 sasikishore.k 2018-07-03 12:38:58 UTC
Hi,

Thank you for prompt response.

I am sorry, I have mentioned the versions wrongly. It is Apache/2.4.25 (Unix) and Apache/2.4.23 (Unix).

Thanks,
Sasi
Comment 3 Eric Covener 2018-07-03 12:49:13 UTC
What do the logs say that make you think it's a bug in httpd?
Comment 4 sasikishore.k 2018-07-03 13:07:08 UTC
In the ajp log, can see the below messages.

Here httpd and tomcat are running fine. But on 2 time on 7th june and 2 times on 8th June there was return code 500.

[07/Jun/2018:08:41:44 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1" 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
[07/Jun/2018:09:24:45 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1" 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
[08/Jun/2018:09:15:32 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1" 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
[08/Jun/2018:11:35:42 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1" 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"

As we are getting 500 here, the client (consumer of this request) marking it as disconneted and trigger some disconnet flows.

Thanks,
Sasi
Comment 5 Eric Covener 2018-07-03 13:16:28 UTC
(In reply to sasikishore.k from comment #4)
> In the ajp log, can see the below messages.
> 
> Here httpd and tomcat are running fine. But on 2 time on 7th june and 2
> times on 8th June there was return code 500.
> 
> [07/Jun/2018:08:41:44 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1"
> 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
> [07/Jun/2018:09:24:45 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1"
> 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
> [08/Jun/2018:09:15:32 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1"
> 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
> [08/Jun/2018:11:35:42 +0200] "POST /bppmws/api/provider/heartbeat HTTP/1.1"
> 500 532 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0_102)"
> 

What does the errorlog say? What do the diagnostics on the backend service say?
Comment 6 sasikishore.k 2018-07-03 13:55:39 UTC
In error_log file,

[proxy_ajp:error] [pid 19167:tid 140469388375808] (104)Connection reset by peer: AH01030: ajp_ilink_receive() can't receive header

[proxy_ajp:error] [pid 19167:tid 140469388375808] [client X.X.X.X:58284] AH00992: ajp_read_header: ajp_ilink_receive failed

[proxy_ajp:error] [pid 19167:tid 140469388375808] (120006)APR does not understand this error code: [client X.X.X.X:58284] AH00878: read response failed from 127.0.0.1:8009 (127.0.0.1)

Thanks,
Sasi
Comment 7 sasikishore.k 2018-07-20 10:11:33 UTC
Any updates? This is a production issue for us.

Thanks,
Sasi
Comment 8 Eric Covener 2018-07-20 10:56:10 UTC
(In reply to sasikishore.k from comment #7)
> Any updates? This is a production issue for us.
> 
> Thanks,
> Sasi

Sounds like you're looking for support, but bugzilla is for reporting bugs. There's nothing here yet that implies a bug in httpd. You'll have to troubleshoot the connection between tomcat and httpd.