Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-1197

Received unsolicited state from node X for segment Y of cache Z

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.1.0.DR6
    • 7.1.0.DR5
    • Clustering
    • None

    Description

      Hi,

      we're occasionally seeing these warnings in the server logs:

      [JBossINF] [0m[33m08:20:45,364 WARN  [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar
...
[JBossINF] [0m[33m08:21:02,793 WARN  [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node.

      The warnings seem to be harmless.

      This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-6012 Too many warnings about unsolicited state during cluster shutdown

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5441 Received unsolicited state from node X for segment Y of cache Z

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              rjanik@redhat.com Richard Janik
              Daniel Cihak Daniel Cihak
              Daniel Cihak Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: