Integration with Oracle Wallet causes sporadic database connection failures under high load

Solution Verified - Updated -

Issue

We are encountering problems with our JDBC connections using our Oracle Wallet authentication store. In general, we have our JDBC connector configured to use a wallet for client authentication, but this occasionally fails under high load. Commonly, we see exceptions to the effect of encountered a problem with the Secret Store. Check the wallet location for the presence of an open wallet. However, the exception types encountered vary as well. We've noticed that each instance of this appears to coincide with an invocation of a hibernate list query. We've also seen indications that this may be due to an overwhelmed single threaded implementation of the wallet. We'd like to inquire as to whether this is a known issue, if there is something particular to Hibernate's list query that causes new JBDC connections to be created when normally existing pooled connections would be used, if there are known workarounds, or if there are other things we can do to prevent this exception from occuring.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5
    • 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.