Kbase 16152: Known issues: WebSpeed(1.0) Transaction Server Manager
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Known issues: WebSpeed(1.0) Transaction Server Manager
There are known issues with the WebSpeed Transaction Server Manager,
wtbman, that will not be fixed for WebSpeed Version 1.0 FCS. These
issues exist on AIX, Solaris, and Windows NT.
ISSUE:
You cannot stop all the agents connected to a specific broker by using
the stop # option with the wtbman command. This will only reduce the
number of agents running to be a number equal to the StartInstances
parameter in the wtb.cnf file. You need to use the stop pid option
to stop the remaining agents, specifying each process id separately.
NOTE: This is NOT a bug. This functions as coded, and will not be
changed.
Example:
There are currently 5 agents connected to the WebSpeed broker. The
StartInstances parameter in the wtb.cnf file is set at 2. Use the
following steps to stop all the agents.
1> First, check the status of the broker and agents.
tobago> wtbman 6023 status
Port Number PID State
================================
1031 11758 AVAILABLE
1033 11757 AVAILABLE
1030 11756 AVAILABLE
1042 11508 AVAILABLE
1043 11511 AVAILABLE
2> Next, stop 3 agents using the stop # option with wtbman.
tobago> wtbman 6023 stop 3
3> Check the broker status to make sure the agents were stopped.
tobago> wtbman 6023 status
Port Number PID State
================================
1042 11508 AVAILABLE
1043 11511 AVAILABLE
4> Now, stop the remaining agents by specifying the process id of each
agent separately with the wtbman command.
tobago> wtbman 6023 stop pid 11508
tobago> wtbman 6023 stop pid 11511
5> Finally, check the status again to make sure all agents are now
stopped.
tobago> wtbman 6023 status
Port Number PID State
================================
NO Agents: WTB has no agents in its process pool
Check the error log file /usr1
csa/httpd/cgi-bin/sandbox3/error.log
for details
ISSUE:
If you stop all of the agents that are connected to a specific
WebSpeed broker, no Web requests can be satisfied until an agent is
started manually using the start # option with wtbman. If a user
attempts a connection through a Web Browser, the following message
will be displayed in the Browser.
WebSpeed error from Messenger process.
All WebSpeed Agents are busy serving other requests. Please try again
later.
If this occurs, follow these steps to correct this condition.
1> First, check the status of the broker and agents.
tobago> wtbman 6023 status
Port Number PID State
================================
NO Agents: WTB has no agents in its process pool
Check the error log file /usr1
csa/httpd/cgi-bin/sandbox3/error.log
for detail
2> Now, start the number of agents you want. In this case, 3 agents
will start.
tobago> wtbman 6023 start 3
3> Finally, check the status again to make sure the agents are
available.
tobago> wtbman 6023 status
Port Number PID State
================================
1030 12044 AVAILABLE
1031 12043 AVAILABLE
1033 12131 AVAILABLE
ISSUE:
This issue is similar to the issue above. If any number of agents are
stopped using the stop pid option with wtbman, the number of remaining
agents connected to the WebSpeed broker then becomes a soft limit for
MaxInstances. This means that if all the current agents are busy, a
new agent process will not start automatically to satisfy a web
request. An agent process can be started manually by using the start
# option with wtbman.
NOTE: The last two issues are symptoms of the SAME bug. It IS a bug
and will be fixed in a patch release.
20-Sep-96
Progress Software Technical Support Note # 16152