- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] Even though both Schedule and File Triggers met the requirements to initiate the script execution, it did not start. To investigate the cause, where should I be looking at?
Search via FAQ No.
[DataSpider Servista] Even though both Schedule and File Triggers met the requirements to initiate the script execution, it did not start. To investigate the cause, where should I be looking at?
Even though both Schedule and File Triggers met the requirements to initiate the script execution,
it did not start. To investigate the cause, where should I be looking at?
it did not start. To investigate the cause, where should I be looking at?
- Category :
Answer
+Assumed Cause
The monitoring process is processed by executing a thread
(Monitoring Thread) dedicated to check whether each trigger
(Schedule, File, and AppFabric Triggers) met the requirement
to initiate the script execution.
When "Out of Memory" error occurs in DataSpiderServer,
the Monitoring Thread may shut down from failure to secure
the required memory.
In this case, the monitoring process by the thread cannot
be executed, resulting in a condition in which the script
failing to execute regardless of whether it meets the requirement.
Moreover, the Monitoring Thread is created only when
DataSpiderServer is initiated.
+How to Check
Please check the server.log, server.error.log, or the XML log
to see whether "Out of Memory" error occurred.
Moreover, an event of trigger stopping is written in
the server.log starting from the version 2.4.4 as a result
of the following fix:
-If the following triggers cannot be executed because
"OutofMemoryError" occurred in DataSpiderServer,
the message will appear as "FATAL" level in the server.log.
The triggers are as follows:
- Schedule Trigger
- File Trigger
- AppFabric Trigger
The message will appear as follows:
"<Trigger Name>trigger task was terminated."
+Workaround
In order to return the Schedule, File, and AppFabric Triggers
back to a state ready to initiate the script execution, restart DataSpiderServer.
+Troubleshoot
You must resolve the error that occurred when the Monitoring Thread stopped.
In most cases, "Out of Memory" error in the script is the cause.
To deal with this case, please reference FAQ 24257.
*The link is posted in Reference.
+Required Information for Inquiry
If the script is not executing by the trigger in spite of no error,
or the cause of the error is unknown, please send an inquiry to
our support center with the following information:
-Log
${DataSpider.home}/server/
logs/server.log
${DataSpider.home}/server/logs/server.error.log
If you can determine in which script the error occurred,
please download and send the Execution Result from My Log.
-Occurrence Time
Tell us the time when the Schedule, File, and AppFabric Triggers
were supposed to initiate the script execution. Moreover, if you know
the error was occurring in the script, tell us the time when it occurred.
-Project
If the error is occurring in the script, please download and send the project
that includes the script from My Project.
*Please specify the version in which the error occurred before downloading.
-Trigger Settings
Please send a screen capture of every setting of the trigger
that failed to initiate the script execution.
From the version 3.0, because you can specify and export the trigger,
you can just send the trigger file you exported.