Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices

When using mapped or UNC links, the MTA automatically starts one high priority scanner thread for the priority 0 and 1 subdirectories of its input queues. It also starts a second scanner thread for the priority 2-7 subdirectories. This default configuration can create a bottleneck under some circumstances:

• The priority 0 subdirectory is used for Busy Search requests from GroupWise client users. The priority 1 subdirectory is used by GroupWise Remote users. If your GroupWise system serves a large number of very active GroupWise Remote users, the MTA can stay busy processing requests from Remote users, causing other users to experience a delay in response to a Busy Search request.
• The priority 2 subdirectory is used for administrative messages and high priority user messages. Priority 3-7 subdirectories are used for regular and low priority messages and status messages. Certain administrative activities, such as moving a large number of users or purging trash, can create numerous administrative messages in the priority 2 subdirectory, causing users to experience a delay in receiving high priority as well as regular messages.

For the locations of the MTA input queues, see Message Transfer/Storage Directories in Troubleshooting 3: Message Flow and Directory Structure.

You can configure the MTA so that it starts separate scanner threads to service the priority 1 and 2 subdirectories and/or separate scanner threads for the 2-3 and 4-7 subdirectories.

IMPORTANT:  Do not try to run more than one MTA for the same domain.

1. In ConsoleOne, browse to and right-click the MTA object > click Properties.

2. Click GroupWise > Agent Settings to display the Agent Settings page.

   
   

3. Select Use 2nd High Priority Scanner to provide separate MTA scanner threads for Busy Searches and GroupWise Remote users.

4. Select Use 2nd Mail Priority Scanner to provide separate MTA scanner threads for administrative messages and high priority user messages vs. regular and low priority messages.

   These settings can be used separately (creating three MTA scanner threads) or together (creating four MTA scanner threads).

   Primary Use	Priority Directory	Default Operation	2nd High Priority Scanner	2nd Mail Priority Scanner	Both Second Priority Scanners
   Busy searches	wpcsin\0	High priority scanner thread	High priority scanner thread one	High priority scanner thread	High priority scanner thread one
   GroupWise Remote user requests	wpcsin\1		High priority scanner thread two		High priority scanner thread two
   Administrative requests and high priority messages	wpcsin\2	Mail priority scanner thread	Mail priority scanner thread	Mail priority scanner thread one	Mail priority scanner thread one
   High priority statuses	wpcsin\3
   Normal priority messages	wpcsin\4			Mail priority scanner thread two	Mail priority scanner thread two
   Normal priority statuses	wpcsin\5
   Low priority messages	wpcsin\6
   Low priority statuses	wpcsin\7
   Total Scanner Threads in Use:		2	3	3	4

5. Click OK to save the new scanner thread settings.

   ConsoleOne then notifies the MTA to restart so the new setting can be put into effect.

Corresponding Startup Switches:
You could also use the /fast0 and /fast4 switches in the MTA startup file to adjust the allocation of MTA scanner threads.