qrtz_triggers and qrtz_fired_triggers tables do not contain immediate triggers created by org.quartz.Scheduler#triggerJob(org.quartz.JobKey, org.quartz.JobDataMap)

[devurandom]

I am running Quartz 2.5.0 with following properties:

org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
org.quartz.jobStore.dataSource=<name of a data source I set up using `org.quartz.utils.DBConnectionManager#addConnectionProvider`>
org.quartz.jobStore.tablePrefix=QRTZ_
org.quartz.jobStore.isClustered=true
org.quartz.jobStore.useProperties=true
org.quartz.jobStore.misfireThreshold=60000
org.quartz.jobStore.clusterCheckinInterval=15000

I trigger jobs for immediate execution using org.quartz.Scheduler#triggerJob(org.quartz.JobKey, org.quartz.JobDataMap). These jobs take several minutes, so I do have time to inspect the database tables.

Based on my observations of periodic triggers and the code of org.quartz.core.QuartzScheduler#triggerJob(org.quartz.JobKey, org.quartz.JobDataMap), I would expect:

1. Right after the trigger was fired, I would expect a row in the qrtz_triggers table with trigger_name LIKE 'MT_%' (cf. org.quartz.core.QuartzScheduler#newTriggerId) and with job_name being the name of the job I am trying to execute.
2. A bit later, I would expect the qrtz_fired_triggers to contain a row with the trigger_name and job_name I saw in qrtz_triggers, and qrtz_fired_triggers.state = 'ACQUIRED', and the row in the other table to change to qrtz_triggers.state = 'ACQUIRED'.
3. While my job executes, I would expect to see qrtz_triggers.state = 'BLOCKED' and qrtz_fired_triggers.state = 'EXECUTING'.

However, neither qrtz_triggers nor qrtz_fired_triggers appear to contain any hint of the job scheduled for immediate execution. Why is this?

If this is not a problem with my configuration, how can I achieve such "trace" of executing jobs?