Message Processed by a Custom Processor Group Remains in ScribeIn for Longer Than Expected
Article ID: KB0078521
Updated On:
| Products | Versions |
|---|---|
| TIBCO Scribe Insight | 7.9.2 |
Description
There is a delay in processing messages when using a custom processor group. When using the DEFAULT processor group, messages are picked up from the ScribeIn queue and are processed within seconds. When using a custom processor group, messages come into the ScribeIn queue and can take up to 30 seconds to move to the MSMQ “in” queue associated with the custom processor group.
Issue/Introduction
Messages processed by a custom processor group remain in ScribeIn for longer than expected. The DEFAULT message Dispatch Delay can be modified by inserting the parameter in the Scribe Internal database KSYNC table.
Resolution
By default, the dispatch delay default setting is set to 30 seconds. The setting can be modified by inserting the parameter setting into the KSYNC table in the Scribe Internal Database and specifying the dispatch delay seconds.
- Ensure you have a backup of the SCRIBEINTERNAL database.
- Run the following SQL query on the SCRIBEINTERNAL database:
INSERT INTO [SCRIBEINTERNAL].[SCRIBE].[KSYNC]([SECTION],[KEYNAME],[KEYVALUE])VALUES('MESSAGESERVER','SETTINGS.MESSAGEDISPATCHDELAY','2')
- The '2' at the end of the query is the delay in seconds.
- Restart the Scribe services.
- Monitor memory and CPU usage on the Scribe server. If you find usage is too high when processing messages, increase the dispatch delay seconds. For example:
UPDATE [SCRIBEINTERNAL].[SCRIBE].[KSYNC] SET KEYVALUE = '10' WHERE SECTION = 'MESSAGESERVER' and KEYNAME = 'SETTINGS.MESSAGEDISPATCHDELAY'
Feedback
Yes
No
Powered by
