I’m running into an issue when trying to start up a compose file in docker where the rabbitmq container is starting right away but not ready for a couple seconds, so when my NSB applications start up, the crash fairly quickly because they can’t connect to the transport. If I run the docker-compose file again, everything is fine because rabbit is ready by then. There’s another work around in the docker community where you add a shell script to keep pinging an endpoint before starting. This super kludgy imo. The recommended practice is that the application retry the connections on it’s own.
I’m assuming the NSB has this functionality but I haven’t been able to locate it. The only docs I’ve come across so far talke retries for the messages themselves, which is something different. So, is there a way to set the retry policy for the connection to the transport?