TIBCO Scribe® Insight Custom Processor Groups are slow to process messages
Article ID: KB0078261
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration - Connect ( Scribe ) | - |
Description
Issue: When a message to be processed by a Custom Processor Group enters into the ScribeIn queue it will wait for ~30 seconds before being moved into another queue. When using a Default group messages are processed immediately.
Issue/Introduction
When using Custom Processor Groups messages in the ScribeIn queue wait for ~30 seconds before being processed
Resolution
This is caused because the message dispatch is on a 30 second wait by default for previous load issues. To change the wait time and process messages faster, please run the following query on the Scribe Internal 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 to wait. You can change this number if you see too much memory/cCPU is being used when processing messages.
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 to wait. You can change this number if you see too much memory/cCPU is being used when processing messages.
Feedback
Yes
No
Powered by
