Quartz Job Description The desired table stored in the database
QRTZ_CALENDARS Calendar Blob type information stored in the Quartz
QRTZ_CRON_TRIGGERS storage Cron Trigger, including Cron expressions, and time zone information
Information QRTZ_FIRED_TRIGGERS store state information associated with the Trigger triggered, as well Trigger group associated Job execution information storage paused QRTZ_PAUSED_TRIGGER_GRPS
QRTZ_SCHEDULER_STATE amount of state information stored relating to the Scheduler, Scheduler and other examples (if it is used in a cluster)
Pessimistic locking QRTZ_LOCKS storing the program information (if using pessimistic locking)
For more information on Job's QRTZ_JOB_DETAILS each configured to store
QRTZ_JOB_LISTENERS information stored about JobListener the configured
QRTZ_SIMPLE_TRIGGERS stores the Trigger simple, comprising a number of repetitions, spacing, and number of times has contacted the
QRTZ_BLOG_TRIGGERS Trigger types are stored as Blob (Quartz for users to use JDBC to create their own custom Trigger type, JobStore do not know how to store instances of time)
Information QRTZ_TRIGGER_LISTENERS configured storage of TriggerListener
Information QRTZ_TRIGGERS configured storage of Trigger
quartz persistent database table fields explain
to build tables, SQL statements in quartz-1.6.6 \ docs \ dbTables folder can be found, introduced to the main few tables:
Table qrtz_job_details: job save the details of the table according to the actual needs of users the initialization
job_name: cluster job name, the name of the user that they can be customized without forcing
job_group: cluster name of the job of the group owning the name user himself free to customize, without forcing
job_class_name: cluster in a note job realization class package name completely, Quartz is based on this path to find the job class classpath
is_durable: if persistent, this property is set to 1, quartz job will persist in the database
job_data: a blob field, job storing persistent objects
Table qrtz_triggers: save information trigger
trigger_name: trigger name, the name of the user that they can be customized without forcing
trigger_group: name of the trigger belongs to the group, the name of the user himself free to customize, without forcing
job_name: qrtz_job_details table job_name foreign key
job_group : qrtz_job_details table job_group foreign key
trigger_state: the current trigger status is set to ACQUIRED, if set to WAITING, then the job will not trigger
trigger_cron: trigger type, use cron expression
Table qrtz_cron_triggers: cron expression table storage
trigger_name: trigger_name the foreign key table qrtz_triggers
trigger_group: qrtz_triggers foreign key table trigger_group
cron_expression: cron expression
table qrtz_scheduler_state: note storage cluster instance information, quartz periodically read the information of the table determines the cluster in the current state of each instance
instance_name: the name of the configuration file before org.quartz.scheduler.instanceId configuration will written in this field, if set to AUTO, quartz name is generated according to a physical machine name and the current time
last_checkin_time: on examination time
checkin_interval: time between inspections
Quartz.properties configuration file:
# dispatcher identifies the name of each instance in the cluster must use the same name = Scheduler org.quartz.scheduler.instanceName
#ID set to automatically obtain each have different = AUTO org.quartz.scheduler.instanceId
# for persistent data storage mode = org.quartz.impl.jdbcjobstore.JobStoreTX org.quartz.jobStore.class
# database platform database alias org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.weblogic.WebLogicOracleDelegate # = myXADS taken lightly org.quartz.jobStore.dataSource
# = QRTZ_ table prefix org.quartz.jobStore.tablePrefix
# setting will not appear in the serialization of the string class class version problem occurs when the BLOB is TRUE org.quartz.jobStore = to true .useProperties
# = Add to true cluster org.quartz.jobStore.isClustered
# schedule instance failure check interval = 20000 org.quartz.jobStore.clusterCheckinInterval
# allowable maximum operating extension time org.quartz.jobStore.misfireThreshold = 60000
Class name org.quartz.threadPool.class #ThreadPool implemented = org.quartz.simpl.SimpleThreadPool
number # = 10 threads org.quartz.threadPool.threadCount
# 5 = thread priority org.quartz.threadPool.threadPriority
# since the creation of the Father = to true thread org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread
# = CT setting data source org.quartz.dataSource.myXADS.jndiURL
#jbdi class name org.quartz.dataSource.myXADS.java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory # URLorg.quartz.dataSource.myXADS.java.naming.provider.url = t3: // localhost: 7001
Note: in the J2EE project If you want to use the relevant information database management Quartz, you must configure the data source, which is Quartz request.
---------------------
Original: https: //blog.csdn.net/fly_captain/article/details/83058147