Optimizing The Routing Queue; Adjusting The Maximum Number Of Active Router Threads; Adjusting The Maximum Number Of Idle Router Threads; Adjusting Mta Polling Of Closed Locations - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

43.3 Optimizing the Routing Queue

Using startup switches in the MTA startup file, you can fine-turn MTA processing in of the routing
queue. When the MTA starts, it starts one or more router threads to process its routing queue
(
gwinprog
parameters you can set.
Section 43.3.1, "Adjusting the Maximum Number of Active Router Threads," on page 694
Section 43.3.2, "Adjusting the Maximum Number of Idle Router Threads," on page 694
MTA Web Console You can view the current contents of the routing queue from the
Click Router under the Queue Information heading.
43.3.1 Adjusting the Maximum Number of Active Router
Threads
By default, the MTA continues to start additional router threads to processes messages in the routing
queue as long as message traffic demands it, until as many as 16 router threads are running. Use the
/maxrouters
start.
Set /maxrouters to a lower number to conserve resources and keep the MTA from starting more than
the specified maximum number of router threads.

43.3.2 Adjusting the Maximum Number of Idle Router Threads

By default, after the MTA starts a router thread, it keeps it running, up to the maximum number
specified by the /maxrouters switch. In a system where short bursts of heavy message traffic are
followed by extended lulls, idle router threads could be consuming resources that would be better
used by other processes. Use the
many idle router threads are allowed to remain running. The default is 16 idle router threads.
Set /maxidlerouters to a lower number if you want the MTA to terminate idle router threads more
quickly. Set /maxidlerouters to a higher number if you want the MTA to keep more idle router
threads ready to process incoming message traffic.

43.4 Adjusting MTA Polling of Closed Locations

When a location becomes closed (unavailable), the MTA waits before attempting to recontact that
location. If the MTA waits only a short period of time, the MTA can waste time and create network
traffic by trying to reestablish a connection with a closed location. On the other hand, you do not
want the MTA to ignore an available location by waiting too long.
By default, the MTA waits 600 seconds (10 minutes) between its attempts to contact a closed
location. You can adjust the time interval the MTA waits to meet the needs of your GroupWise
system.
1 In ConsoleOne, browse to and right-click the MTA object, then click Properties.
2 Click GroupWise > Agent Settings to display the Agent Settings page.
694 GroupWise 8 Administration Guide
). As messages arrive in the routing queue, it starts additional routers as needed, within
switch in the MTA startup file to control the number of router threads the MTA can
/maxidlerouters switch in the MTA startup file to determine how
Status page.