Mirth Connect

Christopher Ro added a comment - 20/May/09 3:52 PM Fixed Dashboard status update issues for VM connector (Channel Reader).

Jacob Brauer added a comment - 21/May/09 3:02 PM Looks like it might not be a bug with the Statuses, but actually a bug with the PollingMessageReceiver. If you stop a File reader, the PollingMessageReceiver calls the following line twice: ControllerFactory.getFactory().createMonitoringController().updateStatus(connector, connectorType, Event.DISCONNECTED); The first time is with the LAST Channel Reader as the connector, and the second time is with the proper File Reader connector as the connector. This doesn't hurt anything besides the connector status, which gets resolved with the next message that comes in.

Jacob Brauer added a comment - 07/Oct/09 3:53 PM Here are some notes from Alberto about the issue: "It's because how the MonitorController searchs the channelId with the component name. BTW I've made an in-deep search, and I've conclude than this is because the endopints definded in the incoming router in the mule-config.xml lacks the connector attribute. IE: This is how a MLLP endpoint is defined: <endpoint address="mllp://127.0.0.1:6635"                      connector="74df15f7-12e7-47f5-a74b-707fe2415492_source_connector"                      synchronous="true"                      transformers="(...)" /> And this is how an incoming VM is defined:     <endpoint address="vm://74df15f7-12e7-47f5-a74b-707fe2415492" transformers="(....)"/> When Mule builds the endpoints from ints attributes. In this process, when the connector does not exists, it tries to find one. For VMConnector, it seems than the last developed is assigned to the endoint. Based on this, all VMReceivers are assigend to the last VMConnecetor created (!!!!!!) So to "solve" it, it's as simple as add this attribute when creating mule-config.xml But this can't be as there is no connector defined for VMReaders. So, IMHO I see the next options: *) Remove the line from the PoolingMessage. The simplest one. or: *) Change MonitorController to instead using the connectorName, use the channelId. This implies to change some callers, but I think this is the real solution. or: *) Create a VMConnector for each VMReceiver in the mule-config, and add the connectorName propertie to this endpints."

Jacob Brauer added a comment - 09/Oct/09 11:55 AM Commented out the updateStatus line in the PollingMessageReceiver because other channels could share the same VMConnector and change their status.