Uploaded image for project: 'InsightEdge Platform'
  1. GS-13569

Log fills up with "unmarshalling failure" messages when a cluster partition member is unreachable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 12.3.1
    • Labels:
      None
    • Platform:
      All
    • Acceptance Test:
      monitor log output on disconnect
    • Sprint:
      12.3.1-RC1
    • Product:
      XAP
    • Edition:
      Open Source

      Description

      It was the intention of the RegistrarProxy.handleException to rethrow the exception if it is an Error, unless it is a LinkageError, OutOfMemoryError, or StackOverflowError. Otherwise print the exception stack trace if debugging is enabled.

      The following printout is done in INFO instead of debug -

      INFO [com.sun.jini.reggie] - unmarshalling failure; Caused by: java.io.NotActiveException: Failed to retrieve proxy from service, cause Connect Failed to [NIO://192.168.33.10:49706/pid[860]/1212233883811_3_286485615364391954_details[class com.gigaspaces.internal.server.space.SpaceImpl(foo_container1_1:foo)]]; nested exception is:
              java.io.IOException: java.net.SocketException: Host is down

      Move this log to level FINEST, configurable by
      com.sun.jini.reggie.level = FINEST

        Attachments

          Activity

            People

            • Assignee:
              moran Moran Avigdor
              Reporter:
              moran Moran Avigdor
              Participants of an issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: