JBoss XA Transactions Causing Contention and Extended Latch Wait Times on IBM UDB DB2
Issue
XA transactionsfrom JBoss are causing contention onIBM UDB DB2- Contention is leading to extended latch wait times
- Explicitly
SQLO_LT_SQLP_XID_HASH_BUCKET_xregHshLatchis causing the contention - Multiple transactions are writing to a single bucket or address space
JBoss correctly generates unique XIDs for XA transactions, so why does this occur?
Environment
- Red Hat JBoss Enterprise Application Platform 7.4.20
- IBM DB2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
