ddd4j-javalin MQ

Overview

Covers MQClient, listeners, required/optional, ACK, retry, readiness, rollback, and close uniformly. Confirm the maintenance line with ddd4j-javalin-version-selection first, then read the current branch source.

When to Use

• Registering MQ clients and listeners as JavalinLifecycleParticipants with explicit required-versus-optional classification on 6.7.x, 7.1.x, or 7.2.x.
• Implementing the readiness contract: required-consumer failure blocks startup or readiness, optional-consumer failure degrades status explicitly.
• Implementing acknowledgment semantics — ack after successful business processing, nack with policy-driven requeue — plus backoff, retry limits, dead-letter routing, and message-id idempotency.
• Managing MQ shutdown: stop receiving, drain, and close consumers/connections in reverse registration order with idempotent close.
• Running publish/consume, ack/nack/retry, duplicate, recovery, and shutdown behavior tests against a real broker.

When NOT to Use

Do not use this skill when: