We spent a while tracking down a problem when we start up many services in Docker containers simultaneously - when a client sent a request, we would get responses from multiple services, even though each service should have been bound to its own exchange.
We tracked the problem down to here: https://github.com/apache/qpid-proton/blob/8ddf5399013b02f1fd13bda3fee7886bd48a98be/cpp/src/uuid.cpp#L45 When you're starting services in Docker containers, they all get the same PID - so if you're starting a bunch of Docker containers simultaneously, the odds are good that the seed will be the same across several of the services. We were even seeing this problem across multiple hosts when the deployment would push out a new build. We've worked around the issue by adding service identifiers and our own unique identifier using std::mt19937_64. I imagine our multi-container situation is the only use case where this error would be common, but with a lot of users, I would think that there would be intermittent issues. Is this something I should open a ticket for? I don't have a patch for proton - I don't know if using std::mt19937_64 is acceptable for the proton code base. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
