Open Daudimania opened 1 year ago
I suspect you will need to provider more instructions on this. e.g. channels, docker compose files, etc. I doubt NG will look at this... maybe someone in the community will. (I don't work for Nextgen)
Also, did you validate it does work in a non container set up?
Thanks for the quick response.
This post is the basic guide to follow for the channels. It closely follows our setup, we just have more channels/a different template for the messages. Also note that the guide does not have mirth in a container, but I provided further setup instructions for the containerized version.
This bug was found when my org was attempting to containerize all of our applications from having them installed directly on the host. We have the same issues running on the host with the most recent versions of both applications. It was just listed as the containerized version to reflect the workaround state.
I don't think that article ever worked (I think someone else posted that on the forums at some point).
Odd. It ended up working for us. The main difference is we use the updated plugins, and our connection settings only has the host name provided instead. We were able to get the full system working on 3.12.0, but using anything 4.x and up caused failure with no logs reported.
LOL, then I take that back, my bad.
So containerized or not, it does now work now, got it.
Describe the bug When using Mirth Connect 4.3.0 in a docker container and using RabbitMQ 3.11.15 also in a docker container, the Mirth JMS Queue does not send messages to RabbitMQ.
To Reproduce Setup steps (if required). Example:
Steps to reproduce the behavior:
Expected behavior A log of an attempt to send the message to RabbitMQ is found in Mirth A connection is recorded between Mirth and RabbitMQ
Actual behavior No obvious attempt to send the message to RabbitMQ from Mirth is found, and the message stays in the queue
Environment:
Workaround(s) With the exact same setup from above, everything works on Mirth 3.12.0
Additional context