No announcement yet.

[MirthConnect3] change in response behaviour compared to MC2

  • Filter
  • Time
  • Show
Clear All
new posts

  • [MirthConnect3] change in response behaviour compared to MC2


    I have a channel that receives a query, lets say "Query Channel".

    In Mirth2 it was quiet easy:
    This query is forwarded by the first destination ("send to HIS") to a MLLP listener.
    The response of this MLLP listener was then resend to the channel ("Query Channel").
    Because the query has a PID segment, the first destination ("send to HIS") filters out the message.
    The second one ("respond to source") took the response and converted it to the according format for the requester.

    In mirth3 I have a problem:
    The query is forwarded by the first destination ("send to HIS") to a MLLP listener.
    Now I cannot tell the first destination to send the received response to the very same channel or the second destination, or can I?

    thank you and very best regards

    EDIT: in the meanwhile I messed up my channel completely. in the new "edit response" of the first destination ("send to HIS") I added this line:
    router.routeMessageByChannelId(channelId, response.getMessage() );
    The problem is, that it is now in an endless loop and remains in the first destination with Status "pending".
    Last edited by gkittlaus; 03-10-2014, 07:36 AM.

  • #2
    Why are you trying to route a message back through the same channel? That's definitely not recommended (as you saw, that creates an infinite loop); there's always a better way to do it.

    You can send a message using a TCP Sender, and then in the next destination retrieve the response from a previous destination and use it. That was true in 2.x as well. It's very likely that you have some misunderstanding about channel/filter logic, or there's some configuration error in your channel. If you post the channel here, it will be easier to troubleshoot.
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

    - How do I foo?
    - You just bar.