Frequently checked "Connection Available?" trait leaves monitored datasource in a bad state
Issue
- Frequently checked "Connection Available?" trait leaves monitored datasource in a bad state
- Since JBoss Operations Network is used to monitor EAP 6.1 servers with datasources, connections in jdbc pools are corrupted after a few days;
Environment
- Red Hat JBoss Operations Network (JON) 3.2.0
- Red Hat JBoss Enterprise Application Platform (EAP) 6.1 - in standalone mode;
- Datasources are monitored with JBoss ON and "Connection Available?" trait is enabled and configured to be checked frequently (for instance 5 minutes);
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.