E1: ORCH: Quartz Scheduler Resilience Not Working E1.Scheduler NoAuth Authentication or Authorization Failed. (Doc ID 2731259.1)

Last updated on MARCH 20, 2023

Applies to:

Symptoms

Quartz Scheduler resilience not working

Currently customer is utilizing orchestrator and the quartz scheduler. They are seeing that even though AIS says that it's starting the scheduler upon startup, when checking via the pingScheduler REST api it isn't actually started. Also when viewing the status from the Orchestrator Studio Scheduler app shows not started.  They need to manually start it using the scheduler/start API which does work and from then on it works properly.  

The following exception was found in the e1root.log

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.