From: New Java 456 on
Hi,

Can anyone advise me on timeouts for Apache, WebLogic, et al?
Basically, how long can a client block waiting for data from the
server. (like PASV mode in FTP?).

Thanks,
Tim
From: New Java 456 on
On Jun 15, 1:52 pm, New Java 456 <newjava...(a)gmail.com> wrote:
> Hi,
>
> Can anyone advise me on timeouts for Apache, WebLogic, et al?
> Basically, how long can a client block waiting for data from the
> server. (like PASV mode in FTP?).
>
> Thanks,
> Tim


Looks like its default to one minute if the following setting is the
one being used. Not clear if this is with or without keepalive but I
guess its with it. Also, the read timeout is configurable with Flex/
Flash. So, the other questions are how Apache does it and also if
something else can time it out such as lost network connection.

HTTPS Duration: The amount of time this server waits before closing
an inactive HTTPS connection

Does this look correct?
From: Captain Obvious on
??>> Can anyone advise me on timeouts for Apache, WebLogic, et al?
??>> Basically, how long can a client block waiting for data from the
??>> server. (like PASV mode in FTP?).

I'm pretty sure client can wait for quite a long time, especially is server
have already sent headers.

NJ> Looks like its default to one minute if the following setting is the
NJ> one being used. Not clear if this is with or without keepalive but I
NJ> guess its with it. Also, the read timeout is configurable with Flex/
NJ> Flash. So, the other questions are how Apache does it and also if
NJ> something else can time it out such as lost network connection.

What are you trying to do? Are you dissatisfied with defaults or something
else?

NJ> HTTPS Duration: The amount of time this server waits before closing
NJ> an inactive HTTPS connection

NJ> Does this look correct?

HTTP and HTTPS are different things.

From: Arne Vajhøj on
On 15-06-2010 13:52, New Java 456 wrote:
> Can anyone advise me on timeouts for Apache, WebLogic, et al?
> Basically, how long can a client block waiting for data from the
> server. (like PASV mode in FTP?).

A very long time.

Otherwise long poll would not work.

Arne
From: Paul Cager on
On Jun 16, 2:46 am, Arne Vajhøj <a...(a)vajhoej.dk> wrote:
> On 15-06-2010 13:52, New Java 456 wrote:
>
> > Can anyone advise me on timeouts for Apache, WebLogic, et al?
> > Basically, how long can a client block waiting for data from the
> > server. (like PASV mode in FTP?).
>
> A very long time.
>
> Otherwise long poll would not work.
>
> Arne

Yes, although if you've got an HTTP proxy between the client and
server you _might_ find that the proxy resets the connection if it
doesn't see a response for a long time.

Tim - have we interpreted your question correctly? I wasn't too sure
of your meaning. If an HTTP server accepts a connection but doesn't
reply it is usually the client that decides to time out.