Uploaded image for project: 'Spring AMQP'
  1. Spring AMQP
  2. AMQP-287

Cannot Connect (no server response) prevents container start

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 1.1.3
    • Fix Version/s: 1.2.0.M1
    • Component/s: RabbitMQ
    • Labels:
    • Environment:
      Linux

      Description

      The issue is caused by missing machines (no machine at at the target IP/crashed server) or network/firewall issues causing connectivity issues, specifically dropped packets.

      It should be noted that windows vs linux behave differently on the missing server case - windows apparently gives some response that the container is happier with and it will go into the retry cycle. On linux missing server or any other cause of dropped packets will cause the below error. This can be simulated easily on a linux machine with

      sudo iptables -A OUTPUT -p tcp --destination-port 5672 -j DROP

      (adjusting port as necessary)

      See referenced forum thread for additional details

        Attachments

          Activity

            People

            • Assignee:
              grussell Gary Russell
              Reporter:
              jrussell J. Russell Smyth
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: