Uploaded image for project: 'Spring Data GemFire'
  1. Spring Data GemFire
  2. SGF-556

Include Pool connection test logic during startup to verify the validity of the configuration

    XMLWordPrintable

    Details

      Description

      Currently, when a user configures a Spring, GemFire cache client application, s/he typically configures a GemFire Pool to distribute (forward) data access operations between the client Region PROXIES and the actual server Regions managing the data.

      However, if the Pool is not configured properly (e.g. wrong host/port specifications), neither GemFire nor Geode fails (fast) on startup to warn the user of this configuration problem. Instead GemFire/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.

        Attachments

          Activity

            People

            Assignee:
            jblum John Blum
            Reporter:
            jblum John Blum
            Last updater:
            John Blum
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Time Tracking

                Estimated:
                Original Estimate - 0.5d
                0.5d
                Remaining:
                Remaining Estimate - 0.5d
                0.5d
                Logged:
                Time Spent - Not Specified
                Not Specified