This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[BUG] When deploying changes to Mirth Connect installations on two different servers behind a load balancer, the deployment only apply to one server, even though both connect to the same database. #6106
Labels
bug
Something isn't working
Describe the bug
When deploying changes to Mirth Connect installations on two different servers behind a load balancer, the deployment only apply to one server, even though both connect to the same database.
To Reproduce
Expected behavior
Both Mirth Connect instances should reflect and implement the deployed changes simultaneously.
Actual behavior
Only the instance where the deployment originated receives the update. The other instance appears updated but functions with the previous configuration.
Environment (please complete the following information):
Workaround(s)
Need to individual deployed both mirth channels.
The text was updated successfully, but these errors were encountered: