Any ideas on why neither are running? What do I need to check to see what triggers the queue to process?
SOLVED - the custom trigger jar file (and all supporting jar files) needs to be in all of the following Pas_Instance/webapps directories:
master
prod1
rest
search
storage
webapi
workflow
In this case, it was the workflow directory that caused the issue. Unfortunately, no error messages were created in the log. But, given the messages in other areas, the culprit is the inability to instantiate the custom trigger classes.
Go to Settings ->Administration Setup -> Batch Jobs -> Queue
Are the triggers delayed ones ?
Also look at Jobs Log File
Done ALL of those things and 100 more. Added Log entries to the validation scripts and the Custom Trigger. The trigger runs fine when selected as a Workflow Action. Nothing shows up in any of the logs - Jobs, Main, Errors - that would indicate that the batches even attempted to run. Note that the when start time is updated the Jobs log shows the event being queued and it does appear in the System Queue.
The same thing happens if when I use delayed triggers. The queue is updated (no log) but when the scheduled time passes, nothing fires.
SOLVED - the custom trigger jar file (and all supporting jar files) needs to be in all of the following Pas_Instance/webapps directories:
master
prod1
rest
search
storage
webapi
workflow
In this case, it was the workflow directory that caused the issue. Unfortunately, no error messages were created in the log. But, given the messages in other areas, the culprit is the inability to instantiate the custom trigger classes.
Thanks for sharing the fix information. We will update documentation on custom Java Triggers as needed.