[proxy_http:error] [pid 32555:tid 140212017477376] [client 10.72.228.197:40

[Sudhanshu Srivastava, modificado 11 Anos atrás.]

Hi Friends,

I am using Liferay 6.1 with JBoss 7 and I am hetting following error

[Sat Feb 16 15:48:16.606809 2013] [proxy_http:error] [pid 32555:tid 140212017477376] [client 10.72.228.197:40268] AH01114: HTTP: failed to make connection to backend: 10.72.228.164
[Sat Feb 16 15:49:17.719282 2013] [proxy:error] [pid 32555:tid 140211996497664] (111)Connection refused: AH00957: HTTP: attempt to connect to 10.72.228.164:8080 (10.72.228.164) failed
[Sat Feb 16 15:49:17.719311 2013] [proxy:error] [pid 32555:tid 140211996497664] AH00959: ap_proxy_connect_backend disabling worker for (10.72.228.164) for 60s
[Sat Feb 16 15:49:17.719319 2013] [proxy_http:error] [pid 32555:tid 140211996497664] [client 10.72.228.197:54345] AH01114: HTTP: failed to make connection to backend: 10.72.228.164
[Sat Feb 16 15:50:21.658685 2013] [proxy:error] [pid 32555:tid 140212216784640] (111)Connection refused: AH00957: HTTP: attempt to connect to 10.72.228.164:8080 (10.72.228.164) failed
[Sat Feb 16 15:50:21.658707 2013] [proxy:error] [pid 32555:tid 140212216784640] AH00959: ap_proxy_connect_backend disabling worker for (10.72.228.164) for 60s
[Sat Feb 16 15:50:21.658714 2013] [proxy_http:error] [pid 32555:tid 140212216784640] [client 10.72.228.197:46927] AH01114: HTTP: failed to make connection to backend: 10.72.228.164

I have no clue that what this issue is for. Please help me friends.

Thanks in advance.

Regards,
Sudhanshu.

[jelmer kuperus, modificado 11 Anos atrás.]

You are using apache httpd in front of liferay and are using mod_proxy_http to serve liferay pages

It tries to connect to your liferay server running on http://10.72.228.164:8080 but it is unavailable

[Sudhanshu Srivastava, modificado 11 Anos atrás.]

Hi Jelmer,

Thanks for the response, I understand the issue.

The application is running fine for 4-5 days then suddenly this error log is encountered. I know the issue but have no idea that why this issue is caused.

Regards,
Sudhanshu.

[jelmer kuperus, modificado 11 Anos atrás.]

you should check the application server logs on 10.72.228.164