My Oracle Support Banner

Quartz Is Executing Scheduled Tasks on All JBoss Cluster Nodes (Doc ID 1344938.1)

Last updated on JULY 21, 2020

Applies to:

Identity Manager - Version 9.1.0.2 to 9.1.0.2
Information in this document applies to any platform.
**Checked For Relevance 25-Jul-2013**

Symptoms

One is running Oracle Identity Manager (OIM) in a clustered JBoss environment. The "Clustering" option has been set to "true" in xlconfig.xml to prevent the Quartz from launching the scheduled tasks on multiple cluster nodes at the same time. However the scheduled tasks are run on both/all cluster members which is causing race conditions and performance problems.

On the JBoss server startup messages you can see following:

...
2011-07-20 11:45:42,332 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler  'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
2011-07-20 11:45:42,332 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 1.5.2
2011-07-20 11:45:42,332 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
...


and later:

...
2011-07-20 14:26:54,448 INFO [SCHEDULER.WEBSTARTUP] Going to start Scheduler
Cluster service
2011-07-20 14:26:54,462 DEBUG [XELLERATE.SERVER] Class/Method:
tcSchedulerClusterService/startService entered.
2011-07-20 14:26:54,462 DEBUG [XELLERATE.SERVER] Schheduler Java Group
Properties :
UDP(mcast_addr=<IP_ADDRESS>;mcast_port=<PORT>;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING(timeout=2000;num_initial_members=3):MERGE2(min_interval=5000;max_interval=10000):FD_SOCK:VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):UNICAST(timeout=5000):pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=4096;down_thread=false;up_thread=false):pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=true)
2011-07-20 14:26:54,462 INFO [XELLERATE.SERVER] Going to Start Scheduler
Cluster Service
2011-07-20 14:26:54,679 INFO [STDOUT]
-------------------------------------------------------
GMS: address is <HOSTNAME>:<PORT>
-------------------------------------------------------
2011-07-20 14:26:56,972 INFO [XELLERATE.SERVER] Scheduler Cluster Service
STARTED
2011-07-20 14:26:56,972 DEBUG [XELLERATE.SERVER] Class/Method:
tcSchedulerClusterService/startService left.
2011-07-20 14:26:56,972 INFO [SCHEDULER.WEBSTARTUP] Going to start Scheduler
Engine
...

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution

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