Configuring JDBC Data Sources. JDBC Connection Pool disabling itself. Hi, During our stress performance test of OSB 10.3g we experience that the JDBC Connection Pool can disable itself, if many statement executions ends in some kind of exceptions (like TimoutException).
As i understand this "disabling" is normal behavior, and eventually it will enable itself again after some time (we have seen this as taking ~10 mins. on an idle environment). In the downtime of the JDBC pool we see a ResourceDisabledException for all JDBC executions on that pool. Since our application correctly handles these exceptions under the XA scope, we would rather disable this "disabling behavior" and have the high availability instead, so the system is online at all time... So my question is; is it possible to switch off this "JDBC Connection Pool disabling"? Optimize & Tuning JDBC Data Source Connection Pool. JDBC Tips. XA Transactions. Most developers have at least heard of XA, which describes the standard protocol that allows coordination, commitment, and recovery between transaction managers and resource managers.
Products such as CICS, Tuxedo, and even BEA WebLogic Server act as transaction managers, coordinating transactions across different resource managers. Typical XA resources are databases, messaging queuing products such as JMS or WebSphere MQ, mainframe applications, ERP packages, or anything else that can be coordinated with the transaction manager. XA is used to coordinate what is commonly called a two-phase commit (2PC) transaction.