Kbase 18770: Web Pages Time Out for 30 Seconds; It's Not the Messenger
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/04/1999 |
|
DRAFT COPY - Currently under review and edit.
INTRODUCTION:
=============
When using WebSpeed 2.1 in an NT server with IIS; if you are able to
receive the web pages to your web browser from an application using
the WebSpeed messenger and the pages are returned almost instantly for
30 consecutive seconds and then it pauses for 30 seconds before the
page is displayed again, you may have another service running which
may be causing this behavior. (Time intervals may vary)
WHY YOU NEED TO KNOW THIS:
==========================
When you first try to see what might be causing this problem, you
might look at the agent status and find one of the Agents in LIMBO
state. Then, you might ask yourself why is the WebSpeed agent in
LIMBO? and if you try to find a reason it will take you some time
depending on your application. Or you might try to query the
messenger only and realize the same time delay occurs, then you might
think the messenger had a time-out. In either case, you may be
spending too much time.
PROCEDURAL APPROACH:
====================
If you have a virgin spare system with only the basics installed where
you can install WebSpeed 2.1 and compare the 2 systems, do so. If you
have the same problem in both systems, this would suggest a possible
problem with the network. If one system works and the other does not,
then you know there is something that needs to be configured in the
system. Before comparing the WebSpeed configuration, start by
stopping other services you might have running. A customer reported
that Print Services for Macintosh was causing this problem in his
system.