Given the code fragment: How are transactions managed?

Question

Exhibit

Options

• Athrough a single shared transaction across the connection factory
• Bthrough a separate transaction per JMS Consumer
• Cthrough a single transaction for the entire JMS Topic
• Dthrough a single shared transaction in the JMS Context

• A
  3% (2)
• B
  2% (1)
• C
  7% (4)
• D
  89% (54)

Explanation

In JMS 2.0's simplified API, a JMSContext encapsulates both the connection and session into a single object, and its transactional state governs all producers and consumers created from it - making D correct: one shared transaction lives in the JMSContext.

Why the distractors are wrong:

• A - The ConnectionFactory is a factory for creating JMSContext objects; it holds no transactional state of its own.
• B - Consumers don't own transactions; they inherit the transactional behavior of the JMSContext that created them.
• C - A Topic is a destination (where messages go), not a transactional boundary; transactions are scoped to the session/context, not the destination.

Memory tip: Think of JMSContext as a "smart session" - it replaced the old Connection + Session pair in JMS 2.0, and like the old Session, it is the single owner of the transaction. If you remember "session owns the transaction," just map Session → JMSContext in the modern API and you'll always land on D.

No community discussion yet for this question.