INTEGRATION_SUITE_CPIadvanced
JMS transaction boundaries and ordered delivery
JMS acknowledgement and database work cannot be assumed to participate in one distributed atomic transaction. A retry can repeat local side effects unless deliberately protected. Ordered processing needs a supported end-to-end design and must not be inferred from queue existence alone.
Overview
JMS acknowledgement and database work cannot be assumed to participate in one distributed atomic transaction. A retry can repeat local side effects unless deliberately protected. Ordered processing needs a supported end-to-end design and must not be inferred from queue existence alone.
Lessons in this topic
- JMS transaction boundaries and ordered deliveryJMS acknowledgement and database work cannot be assumed to participate in one distributed atomic transaction. A retry can repeat local side effects unless deliberately protected. Ordered processing needs a supported end-to-end design and must not be inferred from queue existence alone.
Interview questions covered
- How do you guarantee ordered delivery for messages of the same business object?
- Explain transaction handling with JMS in Cloud Integration.
Related topics
INTEGRATION_SUITE_CPI
Foundations and integration contracts
INTEGRATION_SUITE_CPI
Tenant setup and connectivity
INTEGRATION_SUITE_CPI
iFlow design and message exchange
INTEGRATION_SUITE_CPI
Adapters and protocol contracts
INTEGRATION_SUITE_CPI
Mapping and transformations
INTEGRATION_SUITE_CPI
Groovy and reusable scripts