Include Pool connection test logic during startup to verify the validity of the configuration [DATAGEODE-264]

[spring-projects-issues]

trafficstars

John Blum opened DATAGEODE-264 and commented

Currently, when a user configures a Spring, Apache Geode ClientCache application, s/he typically configures an Apache Geode Pool to distribute (i.e. forward) data access operations between the client PROXY Regions and the actual server Regions managing the data.

However, if the Pool is not configured properly (e.g. wrong host/port specifications), Apache Geode will not fail (fast) on startup to warn the user of this configuration problem. Instead, Apache Geode will not throw an Exception until the first data access operation occurs using a connection from the Pool. This is typically the case when a client (*PROXY) Region has been configured with a specific Pool (most likely to target a specific server group).

As such, this JIRA represents an improvement in SDG to include a "connection test" on the Pool during startup to test a connection with the configured host and port (or hosts and ports) to ensure the configuration is correct before the application completely starts.

By default, the connection test will be disabled to preserve the existing behavior

---

Reference URL: https://jira.spring.io/browse/SGF-556