Hi,
We recently had an issue where an incorrectly configured event listener kicked off over 2million graph instance in just a few hours. Since that has happened, aside from very slow server response time, each time the "Delete Old Debug Files" Archivator is run the graph scheduler and graph listeners stop working.
This is what we see in the logs (full logs for each error are attached):
JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: could not find dataTable with id 'tasksHistoryListTable'
JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: ERROR 40XL1: A lock could not be obtained within the time requested
JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
However when we reboot the server and start the application server the scheduler starts working again...
I have been attempting to run the "Delete old Execution Artifacts" job the clear the excess logs. It had been working to clear out about 30k at a time. But in the most recent run it is attempting to clear about 150k and has now been running for > 24 hours. Also, upon kicking off that instance we again saw the "A lock could not be obtained within the time requested" message in the logs even though the scheduler/listeners are sill working and the Delete Artifacts job still shows as "RUNNING"
So mainly my question is: Would their be an easier way to clear out these excess logs? What would the process be to totally reset the embedded Debry database and start fresh?
Thank you,