Announcement

Collapse
No announcement yet.

Queueing causes undefined messages to destination

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Queueing causes undefined messages to destination

    Using Mirth Connect Server 3.1.1.7461. I have a Mirth channel reader with an HTTP Sender destination set to send JSON messages. There was an issue where the POSTS are not connecting to the listener. The first 51 messages after the error queued perfectly. After being down for 1 hour that the messages started erroring instead of queuing. The error is saying the MRN is missing from the message. For whatever reason it looks like after those first 51 messages the Mirth channel was unable to create the msh handle for the destination and instead of being a JSON message it started sending "undefined" to the destination. There is no difference in the message so this definatly has something to do with queuing and meeting some type of threshold. Any ideas?

  • #2
    Sounds like somewhere in the transformer, there is an "undefined" JavaScript variable.

    I run into this when I use something like ...

    Code:
    var myVar;
    myVar += "something something ";
    ... when it actually needs to be:

    Code:
    var myVar = "";
    myVar += "something something ";
    Feel free to post your channel for someone to take a look.

    -= Jack Haines : Founder/CEO of Healthcare Integrations, LLC
    -= [email protected]
    -= Mirth Connect (Advanced)-certified
    -= Gold member of HL7.org
    -= Available for Mirth Connect channel development and consultation! Schedule a FREE call with me at https://calendly.com/jackhaines

    Comment


    • #3
      I do not believe it's the transformer. If I clone the channel and try running one of the failed messages through the cloned channel the message processes fine to the destination and gets queued as expected. I think it has something to do with the queueing.

      Comment


      • #4
        Can you post the channel you're using?
        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.

        Comment


        • #5
          We redeployed the channel and rebooted the Mirth server and it fixed the issue. As soon as messages started flowing again the error quit.

          Comment


          • #6
            I was poking around in the Mirth server settings and found a setting called "Queue Buffer Size" which appear to be a max size that the queue can grow. Could this be what was causing my symptoms? It's set to "1000" and the messages should have only been a total of 100K but if it includes metadata then I'm not sure what else was in memory.

            Comment

            Working...
            X