Skip to content

fix: QuartzWorkerExecutionManager startup recovery blocks for 30s with composite #588

Description

@mdproctor

Context

QuartzWorkerExecutionManager.onStart() (lines 80–88) blocks on recoverPendingScheduledWorkers() for up to 30 seconds during startup. After the composite WEM change (#461), recovery calls schedulePersistedEvent() on the composite, which now routes using supports() filtering.

The blocking call and its interaction with backend discovery timing needs rework — backends may not all be available when the Quartz startup observer fires at @Priority(20).

Three existing TODOs in QuartzWorkerExecutionManager mark this area as known debt:

  • Line 80: // TODO this must be reworked
  • Line 84: // TODO fix it
  • Line 91: // TODO, yes, here is id of event object...

From

Design review deferred concern §2 in composite WEM spec.

Refs #461

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions