Thanks for the response. It was the timeout in apache that was set to
300. I decided to re architect the issue so that the creation of the
file that is returned is done by a background task.
On Nov 2, 2009, at 12:10 PM, Mark Ritchie wrote:
>
Hey Jeffrey!
First, I would check Apache's configura
There may be a need to actually wait... in that case, spin of the
thread and check out ERXKeepAliveResponse. And see recent discussion
on the Wonder list.
Cheers, Anjo
Am 02.11.2009 um 20:04 schrieb Chuck Hill:
On Nov 2, 2009, at 8:19 AM, Jeffrey Simpson wrote:
I have a direct action
Yea it is a stupid way of doing the job. The call generates a big zip
file for another program to use. I decided to spin off the creation
of the file to a worker thread that will be run periodically and when
the other program ask for the file it will get the last one generated.
On Nov 2, 2009,
On Nov 2, 2009, at 8:19 AM, Jeffrey Simpson wrote:
I have a direct action that can take about 20 min to respond. If I
make the call using direct connect it runs fine. If I make the call
through the Apache Adaptor i get "Empty reply from server" after 5
minutes. I have set the Send, Receive a
On 2/Nov/2009, at 8:19 AM, Jeffrey Simpson wrote:
Does anyone have an idea of what I am missing?
Hey Jeffrey!
First, I would check Apache's configuration to see what it's timeout
is by visiting this url
http://your.web.server.name/server-info?server
(You'd need to enable this in /etc/apache
I have a direct action that can take about 20 min to respond. If I
make the call using direct connect it runs fine. If I make the call
through the Apache Adaptor i get "Empty reply from server" after 5
minutes. I have set the Send, Receive and Connect timeouts to 9000
seconds. When I call WOAda
