users@glassfish.java.net

Re: Problems with Glassfish <-> Apache mod_proxy_ajp

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Wed, 27 Aug 2008 10:56:33 -0400

salut,

glassfish_at_javadesktop.org wrote:
> Dear Glassfish Community,
>
> we are using glassfish v2ur2 in combination with Apache 2.2 and mod_proxy_ajp on our production server. At least once per week, the communication between apache and glassfish seems to come to a halt.
>
> As a result, users cannot load any java-generated pages (it loads for ages until the browser generates a timeout error). In the glassfish log, we see a lot of broken pipe exceptions, and the apache error_log shows the following errors (several hundreds of them, in different combinations):
>

Looks like the connection between mod_proxy_ajp get closed and GlassFish
is unable to write on those connection. When that happens, can you grap
the output of:

% netstat -an | grep 8009

to get the state of the connection?


> [code]
> [Mon Aug 25 13:57:56 2008] [error] (120006)APR does not understand this error code: proxy: read response failed from (null) (localhost)
> [Mon Aug 25 13:57:56 2008] [error] ajp_read_header: ajp_ilink_receive failed
> [Mon Aug 25 13:57:56 2008] [error] (120006)APR does not understand this error code: proxy: read response failed from 127.0.0.1:8009 (localhost)
> [Mon Aug 25 13:57:57 2008] [error] ajp_read_header: ajp_ilink_receive failed
> ...
> [Mon Aug 25 14:01:16 2008] [error] (120006)APR does not understand this error code: proxy: read response failed from 127.0.0.1:8009 (localhost)
> [Mon Aug 25 14:01:22 2008] [error] (110)Connection timed out: proxy: AJP: attempt to connect to 127.0.0.1:8009 (localhost) failed
> [Mon Aug 25 14:01:22 2008] [error] ap_proxy_connect_backend disabling worker for (localhost)
> [Mon Aug 25 14:01:22 2008] [error] proxy: AJP: failed to make connection to backend: localhost
> [Mon Aug 25 14:01:24 2008] [error] proxy: AJP: disabled connection for (localhost)
> ...
> [/code]
>
> Sometimes restarting apache helps to solve the problem, sometimes both apache and glassfish need to be restarted.

Hum...can you get a thread dump of the GF process when than happens? I'm
surprised GF needs to be restarted. Just do:

% jstack PID > thread.dump


>
> BTW, the glassfish stacktrace does not show any busy threads, and there definitely is no garbage collection problem.

ah. Are you able to get pages serviced when invoking GF directly (let's
say on port 8080)?


>
> What can we do to find the cause of this error?

Thanks

-- Jeanfrancois


>
> Kind regards
> Bastian
> [Message sent by forum member 'batzee' (batzee)]
>
> http://forums.java.net/jive/thread.jspa?messageID=295279
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>