2 Replies Latest reply on Oct 10, 2005 5:22 AM by sks4jboss

    ERROR [org.jgroups.protocols.pbcast.NAKACK]

      Hi,

      I have 2 servers in cluster. I am using jboss version 3.2.2. I am continuously getting following errors on the console.

      From server1.log

      2005-10-10 00:37:59,311 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=mach01:57911 (additional data: 19 bytes), local_addr=mach01:57911 (additional data: 19 bytes)) message with seqno=3883 not found in sent_msgs ! sent_msgs=[4539 - 5949]


      From server2.log

      2005-10-10 00:30:28,328 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=mach01:57911 (additional data: 19 bytes), local_addr=mach02:61772 (additional data: 19 bytes)) message with seqno=61528 not found in sent_msgs ! sent_msgs=[65528 - 66005].

      Can someone please help in identifying the issue? What does the above error means?

      Thanks a lot in advance.
      Cheers,
      Suddu

        • 1. Re: ERROR [org.jgroups.protocols.pbcast.NAKACK]
          belaban

          This could be due to a bug changed in JGroups 2.2.5 (from the release notes):

          - Fixed bugs #943480 and #938584. STABLE handles SUSPEND_STABLE and
          RESUME_STABLE events, and STATE_TRANSFER
          sends SUSPEND_STABLE before fetching the state and RESUME_STABLE after
          receiving the state, to prevent
          message garbage collection from going on during a state transfer
          - Fixed bug #938584 (NAKACK.retransmit problem)


          The other JIRA issue I recently fixed is http://jira.jboss.com/jira/browse/JGRP-108. This is in JGroups 2.2.9 (not yet released).

          The problem with JBoss 3.2.2 is that it comes with JGroups 2.2.0, which is not compatible with JGroups 2.2.5, so you cannot simply replace JGroups.
          You will probably need to upgrade, here's a list of JGroups versions shipped with JBossAS: http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsVersionInJBossAS

          • 2. Re: ERROR [org.jgroups.protocols.pbcast.NAKACK]

            Thanks for the Prompt reply.

            Can you please educate us on the impact of this bug? Could this be result in server node getting out of cluster?

            Currently we see that the server nodes come out of cluster environment and we are not sure what could be the problem. Can you please some provide us the pointers so that we can investigate more on this issue.

            Cheers,
            Suddu