Identity Management (MOSC)

MOSC Banner

OIM in warning state due to Scheduler STCUK thread

edited Aug 24, 2017 5:00AM in Identity Management (MOSC) 2 commentsAnswered

<Aug 2, 2017, 4:36:47,173 AM UTC> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,258" seconds working on the request "oracle.iam.scheduler.api.SchedulerService_lp8yuv_SchedulerServiceRemoteImpl", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds in "server-failure-trigger". Stack trace:

Thread-595232 "[STUCK] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {

    -- Blocked trying to get lock: java.lang.Object@10b62558[fat lock]

    org.quartz.core.QuartzSchedulerThread.togglePause(QuartzSchedulerThread.java:158)

    org.quartz.core.QuartzScheduler.standby(QuartzScheduler.java:469)

    org.quartz.impl.StdScheduler.standby(StdScheduler.java:167)

    oracle.iam.scheduler.impl.quartz.QuartzSchedulerImpl.stop(QuartzSchedulerImpl.java:802)

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center