During architecture, design, and implementation, you must carefully consider using Java Message Service’s (JMS) various transaction options. For a simple approach, you wouldn’t use transactions; instead you would use acknowledgement modes, such as automatic, duplicates okay, and client. Another option uses transacted session for sending and receiving messages. Message-driven beans (MDBs) with container-managed transaction demarcation (CMTD) or with bean-managed transaction demarcation (BMTD) provides yet another alternative. This article clearly presents the available transaction options and carefully considers these options’ impact on message redelivery. You’ll gain a better knowledge of using JMS efficiently and effectively.
Transaction and redelivery in JMS
Posted on June 30, 2006
Posted in: Development