-
Documentation
-
Resolution: Done
-
Major
-
6.4.0.GA, 7.0.0.GA, 7.1.0.GA, 7.2.0.GA
-
Documentation (Ref Guide, User Guide, etc.)
-
-
-
Corrected formatting issues.
-
+
This customer issue is not critical to complete for EAP-CD 14 or EAP 7.2.0.GA.
The potential information addition seems related to existing Configuration Guide content. The customer found this issue working with EAP 6.x, but there is no critical reason to backport any additions that far back.
I'd like the assigned writer to confirm if this information is useful to general customers, and if yes, the best location for any new content. I saw mention of TCPPING in the Configuration Guide, Chapter 23. Configuring High Availability, so that may be the best location.
This issue is based on information in this customer escalation in SalesForce:
EN-09432 - https://gss.my.salesforce.com/a3nA000001DDePZ
The user was attempting to use JDBC_PING as part of setting up a JBoss cluster, to use JDBC_PING for initial discovery as opposed to TCPPING, MPING, etc. They found nothing in the EAP docs about how to do this, but did use this KBase article but unsuccessfully: https://access.redhat.com/solutions/691563
Additional customer information from the linked survey response at https://gss.my.salesforce.com/a1aA000000KsvnnIAB :
"- Regular documentation does not cover the topic of JDBC_PING setup.
- Knowledge base article https://access.redhat.com/solutions/691563 is not updated with the information about the latest EAP version.
- Support request was the last resort to get helped."
- is cloned by
-
JBEAP-17400 How to use JDBC_PING for initial discovery of clustered EAP servers
- Closed