How can I minimize the volume of logging due to connection failure warnings during a database outage with JBoss EAP 6?

Solution In Progress - Updated -

Issue

A high volume of messages like the below (perhaps, a few each second depending on application load), each followed by a lengthy stack trace, may be observed in the server log during a database outage:

4:16:52,305 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Thread-131 (HornetQ-client-global-threads-804077561)) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection

This occurs in spite of the fact that application code catches the exceptions raised by data source getConnection() calls.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content