glassfish
  1. glassfish
  2. GLASSFISH-14030

[Shoal] Error needs to be logged when Backing Store is not available on a remote instance

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      14,030

      Description

      When a Backing Store is not available on a remote instance to replicate the
      data, Shoal must log an Exception/Error message, when it tries to use the remote
      Backing Store (for save or remove) to indicate that Replication / Failover will
      Not Work.

      Issues 13945 and 14029 discuss the scenario when remote Backing Stores are not
      available.

        Activity

        Hide
        Mahesh Kannan added a comment -

        Will talk to the GMS team about this. Not sure if the WARNING/Exception can be
        logged when BackingStores are created, but certainly the absence of a
        BackingStore can be detected during gms.sendMessage.

        Will update the issue once we understand what can be done here.

        Show
        Mahesh Kannan added a comment - Will talk to the GMS team about this. Not sure if the WARNING/Exception can be logged when BackingStores are created, but certainly the absence of a BackingStore can be detected during gms.sendMessage. Will update the issue once we understand what can be done here.
        Hide
        Mahesh Kannan added a comment -

        Assigning this to GMS team for logging a WARNING message when a messages arrives
        for a non existent targetToken

        Show
        Mahesh Kannan added a comment - Assigning this to GMS team for logging a WARNING message when a messages arrives for a non existent targetToken
        Hide
        Joe Fialli added a comment -

        Will log a message the first time a message arrives for a targetComponent with
        no MessageActionFactory registered in a CORE member.

        Show
        Joe Fialli added a comment - Will log a message the first time a message arrives for a targetComponent with no MessageActionFactory registered in a CORE member.
        Hide
        Joe Fialli added a comment -

        Created an attachment (id=5201)
        GMS send/receive message monitoring stats per targetcomponent for trade2

        Show
        Joe Fialli added a comment - Created an attachment (id=5201) GMS send/receive message monitoring stats per targetcomponent for trade2
        Hide
        Joe Fialli added a comment -

        Fixed.

        Here is the log event that notifies that a message arrived in a GMS CORE member (all glassfish clustered instances
        are CORE except the DAS) and there is no handler registered to process it. The target component is the
        name of the ReplicationBackingStore type. (web application name for web sessions, ejb class name for ejb, ....)

        GMS1116: unable to deliver message to a non-existent target component

        {0}

        for group:

        {1}

        . Note: only reported for first message.

        Show
        Joe Fialli added a comment - Fixed. Here is the log event that notifies that a message arrived in a GMS CORE member (all glassfish clustered instances are CORE except the DAS) and there is no handler registered to process it. The target component is the name of the ReplicationBackingStore type. (web application name for web sessions, ejb class name for ejb, ....) GMS1116: unable to deliver message to a non-existent target component {0} for group: {1} . Note: only reported for first message.

          People

          • Assignee:
            Joe Fialli
            Reporter:
            varunrupela
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: