Re: [WEB400] V5R1 Classic Woes...

["Nathan M. Andelin" <nandelin@xxxxxxxxxxxxxxxxxxx>]

> From: "Brad Stone" <brad@bvstools.com>
> Ever since we installed V5R1 after a while (seems to be
> inconsistent with time, maybe with bytes served?) a server
> instance will stop responding.

Will it stop responding to requests for static content?  Or is the problem
related to dynamic content only?

> Although the jobs still show they're running, with no
> abnormal messages that I can find.

So, the HTTP Server thinks that it's running normally?

> Ending the HTTP server instance seems to work, but the jobs
> don't end.  Manual ending is necessary.

Isn't that normal behavior if clients are still connected?

> Start them back up and everything is fine.

For how long?

> Anyone else experience this?

Not normally.  But one way to duplicate this behavior is to reduce the
number of HTTP Server threads started (CHGHTTPA Command), and allow
persistent connections.

Netscape Navigator may request up to twelve (12) connections, while Internet
Explorer normally requests two (2).  Each connection is serviced by a
separate thread.  So just a couple users can easily exhaust the number of
active threads.  The next person who tries to connect, gets the hour glass,
and nothing more.

Are you allowing persistent connections (MaxPersistRequest, PersistTimeout)?
What is the maximum number of threads specified in the CHGHTTPA Screen?

Nathan M. Andelin
www.relational-data.com