I'm having an issue using Apache with mod_jk (ajp13) to Tomcat under
JBoss having to do with a request that is taking longer than one of
those pieces thinks is reasonable to produce a result for the client.
I have found an attribute of the Connector called connectionTimeout
specified in service.xml in the jbossweb-tomcat55.sar directory,
along with another value called disableUploadTimeout. It seems to me
that between the two of these parameters, given their descriptions, I
should be able to get around the problem, but I've changed their
values and can't seem to get to a point where the changes I make have
any impact on the problem. Ordinarily, I wouldn't have a request that
takes longer than 5 minutes to execute, but this one is producing a
very valuable report and it just has to take that long. Somebody is
sending an error back to the client after 5 minutes have expired.
It's pretty clear that the server is continuing to chug away at
producing the report, but by the time it's done, no one is listening
for it any more. Does anyone have any insight as to how to make the
timeout in this case longer than 5 minutes? Is there some other
parameter in Apache that's overriding the one I've found in the
Connector? The documentation for disableUploadTimeout says:
This flag allows the servlet container to use a different, longer
connection timeout while a servlet is being executed, which in the
end allows either the servlet a longer amount of time to complete its
execution, or a longer timeout during data upload. If not specified,
this attribute is set to "false".
But it doesn't say where the "longer connection timeout" is
specified. The fact that it says it makes it possible for the servlet
container to use a different, longer connection timeout, makes me
think it means a longer connection timeout than the one specified by
the attribute called "connectionTimeout", but it doesn't say that
specifically.
Help please.
Thanks.
