Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-6036

SonarQube seems to correctly stop but E/S process is still up in some cases

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1
    • Component/s: ElasticSearch
    • Labels:
      None

      Description

      The case was encountered on Nemo:

      • Start the Nemo DB
      • Start a fresh instance of SQ on this DB (i.e. with no index)
      • While E/S is indexing the source lines, run "sonar.sh stop"
        • After some time, SQ seems to have stopped correctly
        • But if you restart SQ, you get an error with:
          org.elasticsearch.transport.BindTransportException: Failed to bind to [XXXX]
          java.net.BindException: Address already in use
          

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ehartmann OLD - Eric Hartmann
                Reporter:
                fabemn OLD - Fabrice Bellingard
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: