Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-2357

ConnectException error messages when using TCP protocol

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.1.2
    • None
    • None
    • Hide
      1. Start the Draw demo using "java -cp jgroups-4.1.1.Final.jar -Djgroups.bind_addr=localhost -Djava.net.preferIPv4Stack=true org.jgroups.demos.Draw -props tcp.xml" (default tcp.xml bundled with JGroups jar)
        • ConnectException for TCPPING: GET_MBRS_REQ cluster=draw initial_discovery=true errors when connecting to port 7801, 7802 and 7803 show up
      2. Start another node with same commandline
        • Both nodes now only show errors of port 7802 and 7803.
      3. Stop the second node by clicking "Leave"
        • ConnectException for ACK message shows up
      4. Start another node and close it (Ctrl+C, etc.)
        • ConnectException for VERIFY_SUSPECT: ARE_YOU_DEAD shows up
      Show
      Start the Draw demo using "java -cp jgroups-4.1.1.Final.jar -Djgroups.bind_addr=localhost -Djava.net.preferIPv4Stack=true org.jgroups.demos.Draw -props tcp.xml" (default tcp.xml bundled with JGroups jar) ConnectException for TCPPING: GET_MBRS_REQ cluster=draw initial_discovery=true errors when connecting to port 7801, 7802 and 7803 show up Start another node with same commandline Both nodes now only show errors of port 7802 and 7803. Stop the second node by clicking "Leave" ConnectException for ACK message shows up Start another node and close it (Ctrl+C, etc.) ConnectException for VERIFY_SUSPECT: ARE_YOU_DEAD shows up

    Description

      When using TCP protocol with JGroups 4.1.1 Final, various kinds of java.net.ConnectException error messages occasionally appear in the log. These exception log messages were by default suppressed with logging level "TRACE" before JGRP-2332 (commit 538a5431b8fd06d644a72f48d584f8114f26a295).

      The ConnectExceptions in this case happen upon attempts to discover nodes, verify node status when another node dies and send ACK when another node leaves.

      The ConnectException messages of node discovery can be avoided by carefully changing configuration of TCPPING or using other ping like JDBC_PING. But the two kinds of messages upon node exiting seem to have no way to avoid.

      Attachments

        Activity

          People

            rhn-engineering-bban Bela Ban
            coolcfan@gmail.com Dante Wang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: