Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12242

Default VERIFY_SUSPECT timeout is too high

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      <protocol type="VERIFY_SUSPECT">
      <property name="timeout">1000</property>
      </protocol>

      Show
      <protocol type="VERIFY_SUSPECT"> <property name="timeout">1000</property> </protocol>

    Description

      In a world where WF starts in 2 seconds on a 2 year old laptop, the default VERIFY_SUSPECT timeout of WF (currently 5 seconds) can easily create the condition where a killed and restarted server shows up in the topology before the old server leaves. Ideally, the VERIFY_SUSPECT timeout should not be longer than the time it takes to start the server process. A timeout of 1 second should suffice.

      Attachments

        Issue Links

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: