Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnection after RabbitMQ shutdown is not successful #60

Open
ghost opened this issue Apr 29, 2016 · 5 comments
Open

Reconnection after RabbitMQ shutdown is not successful #60

ghost opened this issue Apr 29, 2016 · 5 comments

Comments

@ghost
Copy link

ghost commented Apr 29, 2016

I put together a minimal example project illustrating this issue, see the attached zip file. The issue was observed on Windows (running a Docker Host inside a Virtual Box VM) and on Ubuntu.

Steps to reproduce:

  1. Build project: mvn clean install

  2. Run docker-compose up -d in the project's root directory, where the docker-compose.yml file resides

  3. Start the application: java -jar target/lyra-minimal-0.0.0-SNAPSHOT-jar-with-dependencies.jar

  4. Shutdown RabbitMQ: Open a second console, go to the project's root folder and run docker-compose kill rabbitmq

  5. Observe that the application seems to start connection recovery:

    RabbitMQ connection created.
    Done
    Starting RabbitMQ connection recovery...
    
  6. Start RabbitMQ again: docker-compose up -d rabbitmq

  7. Observe that nothing happens in the output of the application

  8. Observe that the application suddenly quits after a few minutes

@ghost
Copy link
Author

ghost commented Apr 29, 2016

lyra-minimal.zip

@neuhaus
Copy link
Contributor

neuhaus commented Jan 24, 2017

What RecoveryPolicy settings do you use?

@neuhaus
Copy link
Contributor

neuhaus commented Feb 16, 2017

I'm also having problems with the Recovery. I use three RabbitMQ servers and they get restarted one after another with a couple of minutes in-between.

According to the logfile, lyra notices the connection loss and recovers all channels, however the communication doesn't work after the recovery.

@dev-konrad
Copy link

@fkbsi , @neuhaus - are you using a TLS connection? I found out I also have a problem with reconnecting, but what's interesting it only happens, when using secured connection.
Autorecovery works OK without encrypted connection.

@neuhaus
Copy link
Contributor

neuhaus commented Jul 8, 2019

I no longer use this software. It‘s only selling point was faulty...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants