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

Session does not reconnect after a ForcedDisconnectException

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      linux , centOS . spring boot

      Description

      Structure: spring boot gemfire server + spring boot gemfire peer

       

      related libs:

      spring-cloud-dependencies : Greenwich.SR5 (spring data gemfire:  2.1.11.RELEASE)

      spring boot:  2.1.10.RELEASE

       

      related config:

      spring.data.gemfire.cache.peer.enable-auto-reconnect= true

      cache is configured by annotation.

      Gemfire session is created by @EnableGemFireHttpSession

      Peer created by @PeerCacheApplication

      Cache Regions are created as beans in java (except session region).

       

      Dev server problem scenario:

      We have weak development server ( for image processing) . When CPU go high , peer cache is disconnected and keep that way. Peer doesnt connect back

      log attached in dev-log.txt

       

      Live server scenario:

      Jvm has assigned 32GB memory. Which is fine. But sometimes jvm does full GC because of filled old gen memory. Looks like GC pause in this case disconnects peer from the cache and keep it in state "disconnected"

      log attached in api-log.txt

       

      Is there way how to make spring boot gemfire reconnect automatically ?

        Attachments

        1. api-log.txt
          44 kB
        2. dev-log.txt
          21 kB
        3. image-2020-04-09-23-43-55-709.png
          image-2020-04-09-23-43-55-709.png
          146 kB

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: