Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 26

Possible Cause: Occasionally, a damaged database in the post office can cause the POA to shut
Possible Cause: Although increasing the number of POA threads from their default settings
Possible Cause: On a NetWare server, Upgrade Low Priority Threads is set to On.
Possible Cause: Another program on the server is interfering with the operation of the POA.
POA Statistics Box Shows Requests Pending
POA Statistics Box Shows Users Timed Out
POA Statistics Box Shows Undeliverable Users
26 GroupWise 7 Troubleshooting 2: Solutions to Common Problems
down.
Action: In ConsoleOne, perform maintenance to correct any problems with the
databases in the post office. See
Databases" and
"Databases" in the
can, in many cases, improve POA performance, creating too many POA
threads can have undesirable results.
Action: For guidance is setting an appropriate number of POA threads, see
"Optimizing the
Administration
Action: The POA might run more smoothly if you set Upgrade Low Priority Threads
to Off. At the server console where the POA is running, type
set upgrade low priority threads=off.
Action: If the POA continues to be unstable, eliminate other programs running on the
server. If the POA is stable when another specific program is not running on
the same server with it, a conflict might exist between the two programs.
Problem: GroupWise client users are using TCP/IP links to the post office. At the POA
console, the Statistics box shows a large number of pending client/server
requests.
Action: Increase the number of POA connections so that more users can be serviced by
the POA. See
Processing" in
Problem: GroupWise client users are using TCP/IP links to the post office. At the POA
console, the Statistics box shows a large number of users timed out.
Action: Having users timed out does not indicate a problem with the POA, but rather a
problem with users. Users who have timed out are users for which the POA
has closed the connection because the GroupWise client was no longer
communicating. Timed out users might not be exiting GroupWise normally or
might be having other problems with their workstations. The number of timed-
out users might tend to increase on a daily basis during the hour after users
leave to go home. This is not a problem.
Problem: At the POA console, the Statistics box shows a large number of undeliverable
users. Undeliverable users can be encountered using either mapped drive
connections or TCP/IP connections. Undeliverable users are counted
differently from undeliverable messages. For example, a single message could
"Maintaining Domain and Post Office
"Maintaining User/Resource and Message
GroupWise 7 Administration
POA" in "Post Office
Guide.
"Adjusting the Number of Connections for Client/Server
"Post Office Agent" in the
Databases" in
Guide.
Agent" in the GroupWise 7
GroupWise 7 Administration Guide.