This article applies to:
- Trustwave MailMarshal (SEG) 6.X and 7.X
- This article does not apply to SEG 8.X or above.
- SEG 8.X and above provide enhanced thread management abilities and a more flexible interface. In these versions, by default engine threads are scaled to fit the number of processor cores on each processing server. For more details, see Help for the Server Threads window.
- Trustwave recommends all customers upgrade to the latest release for enhanced performance and features.
Question:
How do I increase the MailMarshal Engine thread limit beyond the maximum of five threads?
Procedure:
MailMarshal has a GUI-imposed maximum of five Engine threads. Use the registry value listed below to increase the Engine thread number beyond this limit. Increasing the Engine thread number does not assure an improvement in performance. Trustwave recommends this only when directed by Technical Support.
Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Trustwave cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Make sure that you backup your Registry prior to making any changes.
To change the MMEngine thread limit in the registry:
- Backup the registry of the target server. For more information, see Microsoft Knowledge Base Article Q256986.
- Verify if the following registry path exists on the Array Manager:
HKEY_LOCAL_MACHINE\SOFTWARE\Marshal\MailMarshal\Default(1)\Engine
- If this registry key exists, use it to make the change to the Value.
- If it does not exist, add the following registry value on the Array Manager under HKEY_LOCAL_MACHINE\SOFTWARE\Marshal\MailMarshal\Default\Engine:
Data Type = DWORD
Value Name = MaxThreads
Value = Required number of threads (Decimal)
- For full details of the location for each version, see article Q10832.
- Select Commit Configuration Changes to push the update to the node(s).
- Restart the MMEngine service on each node to complete the update.
- This article was previously published as:
- NETIQKB45728