When I was using this interface for model replacement (http://localhost:5005/model, put method), I connected to rabbitmq’s event_broker, but the previous connection was not disconnected, Rasa reopened a connection again, repeatedly Replace, the connection will continue to increase. Is this a bug or is there a problem with my operation method?
please help me 
I don’t see any problems with your log. The rabbitmq connection should not reset when you load a new model so this is not a problem either.
Are you using rasa shell to test the bot locally or rasa run --enable-api to use the REST or socket API?
Normally, the RabbitMQ event queue is used to forward the bot’s tracker store to Rasa X or an analytics system.
I’m using rasa run – enable-api REST, and I’m loading the same model, the rabbitMQ connection count keeps increasing, and if I have to switch the model too often there will be too many useless connections, wasting resources. I think there should be only one connection to maintain.
You should open a github issue. Have you looked at the broker code?
A little bit. I’m looking at the logic that handles the model replacement request. I noticed earlier that rasa directly creates a new broker connection when the model is replaced, whereas the current app instance contains the event_broker property. I don’t know if I misunderstood or what, I’ll go to Github and ask.Thanks for your reply 
