Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2624

JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 5.2.0.Final
    • None
    • Remote Protocols
    • None

      This is issue to distinguish from https://issues.jboss.org/browse/ISPN-2550.

      For logs and more info see related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=875151

      This issue was found during running JDG functional test suite for configuration examples provided with JDG.

            [ISPN-2624] JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered

            Tomas Sykora <tsykora@redhat.com> changed the Status of bug 875151 from ON_QA to VERIFIED

            RH Bugzilla Integration added a comment - Tomas Sykora <tsykora@redhat.com> changed the Status of bug 875151 from ON_QA to VERIFIED

            Tristan Tarrant <ttarrant@redhat.com> changed the Status of bug 875151 from MODIFIED to ON_QA

            RH Bugzilla Integration added a comment - Tristan Tarrant <ttarrant@redhat.com> changed the Status of bug 875151 from MODIFIED to ON_QA

            Tristan Tarrant <ttarrant@redhat.com> changed the Status of bug 875151 from ASSIGNED to MODIFIED

            RH Bugzilla Integration added a comment - Tristan Tarrant <ttarrant@redhat.com> changed the Status of bug 875151 from ASSIGNED to MODIFIED

            2 config files + 2 TRACE log. 2 the same runs, in one was enabled TRACE in "NORMAL" node (started with standalone-ha.xml) and in the second run was enabled TRACE in "STORAGE-ONLY" node (i.e. node started with standalone-storage-only.xml configuration)

            These nodes were build from jdg master December 14.

            Tomas Sykora added a comment - 2 config files + 2 TRACE log. 2 the same runs, in one was enabled TRACE in "NORMAL" node (started with standalone-ha.xml) and in the second run was enabled TRACE in "STORAGE-ONLY" node (i.e. node started with standalone-storage-only.xml configuration) These nodes were build from jdg master December 14.

            Please assign JIRA back to me when confirmed this is an issue in Infinispan.

            Galder Zamarreño added a comment - Please assign JIRA back to me when confirmed this is an issue in Infinispan.

            To recap:

            • According to linked BZ, https://bugzilla.redhat.com/attachment.cgi?id=641649 should not have an endpoint started, but it does have (see references to Hot Rod decoder and Netty). Is this some misconfiguration?
            • NadirX verified that the storage node only configuration works in JDG master as expected, not starting any endpoints.

            So Tomas, can you verify the issue is still present in JDG master?

            If it is, can you attach once again configurations of each server and TRACE logs with org.infinispan category to this JIRA?

            Galder Zamarreño added a comment - To recap: According to linked BZ, https://bugzilla.redhat.com/attachment.cgi?id=641649 should not have an endpoint started, but it does have (see references to Hot Rod decoder and Netty). Is this some misconfiguration? NadirX verified that the storage node only configuration works in JDG master as expected, not starting any endpoints. So Tomas, can you verify the issue is still present in JDG master? If it is, can you attach once again configurations of each server and TRACE logs with org.infinispan category to this JIRA?

              rh-ee-galder Galder Zamarreño
              tsykora@redhat.com Tomas Sykora
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: