Each TIBCO Scribe® Insight Message Processor has a 300MB setting for memory usage.  TIBCO Scribe® Insight operations may occasionally push this limit and it may be necessary to increase this memory allocation.  For Insight release 7.6.2 and above, the registry settings for this memory allocation are controlled from the SCRIBEINTERNAL database.  Keep in mind the server where TIBCO Scribe® Insight is installed needs to have available memory for this change.  If you are using all 8 Message Processors in a Small Business or Standard License, the memory needed will be 8 x 600MB or 4.8 GB just to support the Message Processors.  Similar provisions should be made for Professional and Enterprise licenses which allow more than 8 Message Processors to be active. 

Depending on the integration process that is reaching the limit, you may want to run one of the two scripts below against the SCRIBEINTERNAL database to increase the memory allocation to 600 MB.  There should NEVER be the need to run both scripts.
 
For Queue Integrations, run this script:
INSERT INTO [SCRIBEINTERNAL].[SCRIBE].[KSYNC] VALUES ('MESSAGEPROCESSOR','SETTINGS.MAXMEMORYUSAGEMS','600')
 
For File, Time, or Query Integrations, run this script:
INSERT INTO [SCRIBEINTERNAL].[SCRIBE].[KSYNC] VALUES ('MESSAGEPROCESSOR','SETTINGS.MAXMEMORYUSAGEEM','600')
 
On rare occasions the Message Processor allocation needs to be increased to a higher value, say 900 MB, for which the ‘600’ at the end of each script should be replaced with ‘900’.  Should you continue to hit this memory limit, we recommend you open a case with Support to troubleshoot and rule out a memory leak in your system.
 
Should you still be running an older version of Insight, the settings are located in the registry.  NOTE:  It is strongly recommended that you upgrade your system to a supported version of TIBCO Scribe® Insight.  Should you continue to have issues after making these changes, you will be required to be on a supported version before Support can assist. 

For Insight Version 7.6.1 and earlier:
 
The memory allocation for a Message Processor is controlled via a DWORD registry setting.  Backup your registry before attempting to modify its contents.
 
HKEY_LOCAL_MACHINE\\Software\Scribe\MessageProcessor\Settings

For Queue Integrations:
MaxMemoryUsageMS
 
This setting determines the memory threshold for the MessageProcessor (MP) above which the MP will be shut down. This setting is for MPs started by the MessageServer (queue based). When the MP is started by the MessageServer, the amount of memory the MP is taking up is recorded. At the end of the DTS run, the memory used by the MP is checked again and if it has grown above the initial memory check, and is greater than the number in this setting, the MP is terminated. The default value is 300 (300MB above the baseline, as displayed in the Task Manager’s Mem Usage column.)
 
Open the registry on the Scribe server and go to
HKEY_LOCAL_MACHINE\\Software\Scribe\MessageProcessor\Settings
Right click and select New | DWORD Value.
Value name is MaxMemoryUsageMS
Enter the Value (Example 600 ). Be sure to select the Decimal radio button when entering this value.
 
For File, Time, or Query Integrations:
MaxMemoryUsageEM
 
This setting determines the memory threshold for the MessageProcessor (MP) above which the MP will be shut down. This setting is for MPs started by the EventManager (file, time, and query based). When the MP is started by the MessageServer, the amount of memory the MP is taking up is recorded. Once the DTS run finishes, the memory used by the MP is checked again and if it has grown above the initial memory level recorded and greater than the number in this setting, the MP is terminated. The default value is 300 (300MB above the baseline, as displayed in the Task Manager’s Mem Usage column.)
 
Open the registry on the Scribe server and go to HKEY_LOCAL_MACHINE\\Software\Scribe\MessageProcessor\Settings
Right click and select New | DWORD Value.
Value name is MaxMemoryUsageEM
Enter the Value (Example 600). Be sure to select the Decimal radio button when entering this value.
 
Restart the Scribe services for this setting to take effect.
 

TIBCO Scribe® Insight Message Processor failing.