TIBCO Scribe® Insight (Console)

Error: "The job was terminated because the Message Processor is unresponsive"



Cause: There is a 60 second timeout built into TIBCO Scribe® Insight that is applied to the time the source query is initially executed and the time that the first row is processed into the target. The root cause of this issue is a long-running query in one of the Scribe DTSs. As mentioned earlier, the Scribe Event Manager terminates job processing with a fatal error if a source row or a post DTS script takes longer than 60 seconds to process. This happens because TIBCO Scribe® Insight assumes that the process is hung and should be terminated. There are a variety of reasons for why this might happen (server latency, network latency, etc...).

 

Resolution : Review the source queries and see which ones are taking a long time to run and fix those. These queries could be optimized to improve their performance with just a few updates or indexes or by converting the query to a View in SQL and then using the view as the source

Workaround : Increase the time TIBCO Scribe® Insight waits before ending the slow source query. 
      - It would still be better to improve the performance of the source query but if you have to get the job running now, run the query below against the Scribe Internal database in SQL if you are using Insight 7.6.2 and above:

INSERT INTO  [SCRIBEINTERNAL] . [SCRIBE] . [KSYNC]  VALUES  ( 'EVENTMANAGER' , 'SETTINGS.PROCHANGTIMEOUT' , '600' )

Steps:
- Stop the (5) Scribe Services
- Log into SQL
- Copy and paste the query above
- Run the query against the Scribe Internal Database
- Start the (5) Scribe Services

If this does not resolve the issue, refer to the following article: Queue Storage Limits Exceeded Error: Insufficient Resources to Perform Operation

Error occurs in the TIBCO Scribe® Insight Console, when there is a long-running query in one or more DTS's.