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

Avoid eager creation of a GemFire DistributedSystem in the PoolFactoryBean by creating a ClientCache first.

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Complete
    • 1.6.1 (Fowler SR1), 1.6.2 (Fowler SR2), 1.7 M1 (Gosling), 1.7.4 (Gosling SR4), 1.8 M1 (Hopper)
    • 1.8 RC1 (Hopper)
    • Spring + GemFire Cache Client

    Description

      Currently the SDG PoolFactoryBean class eagerly creates a GemFire DistributedSystem in order to create the GemFire Pool, which is also created before the GemFire ClientCache. However, if the ClientCache were created first, then the SDG PoolFactoryBean would not need to eagerly create a GemFire DistributedSystem, assuming of course that all the SDG interactions and existing functionality/behavior can be preserved.

      By figuring out a solution to this change, it would avoid the awful, dreaded GemFire error...

      java.lang.IllegalStateException: A connection to a distributed system already exists in this VM.  It has the following configuration:
      

      Attachments

        Activity

          People

            jblum John Blum
            jblum John Blum
            Oliver Drotbohm Oliver Drotbohm
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

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