Tuning Transactions
The server incurs additional overhead during two-phase transactions that perform database inserts, updates, and deletes. Two-phase, or X/Open Architecture (XA), transactions in a JMS application involve both the JMS server and the database server. To reduce this overhead, Oracle strongly recommends using the Logging Last Resource (LLR) optimization, as explained in Chapter 4. LLR is a major optimization, and according to Oracle it can double performance when compared to a nonoptimized XA transaction. In particular, LLR is very efficient in cases where a transactional JMS destination is used in conjunction with a JDBC resource. LLR uses a table in the same database to turn this into a one-phase transaction and greatly reduce ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access