Announcement

Collapse

NextGen (Mirth) Connect 3.10.0 Released!

NextGen (Mirth) Connect 3.10.0 is now available as an appliance update and on our GitHub page. This release includes better SQL Server database support, security improvements through fixes and library updates, and improvements for the Advanced Clustering plugin with a focus on improving performance of many of the tasks that are carried out on a frequent interval. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

What to do with ERROR status

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

  • What to do with ERROR status

    I have a Dabasereader to a LLP sender. Occasionally (3 on 290) I get an Error message

    Code:
    ERROR-408: MLLP Connector error
    ERROR MESSAGE:	Can't save payload to queue
    java.lang.NullPointerException
    	at com.webreach.mirth.server.mule.providers.mllp.MllpMessageDispatcher.doDispatch(MllpMessageDispatcher.java:137)
    	at org.mule.providers.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:257)
    	at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290)
    	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
    	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    	at java.lang.Thread.run(Unknown Source)
    What does "can't save payload to queue" mean ??

    How can I retry this action, so nothing gets lost ??

    290 is the total of messages received on the source so there is no large load.

    I checked the ReProcess action on the Error and see that a HL7 message is sent but the status is nog changed to SENT.

    Post edited by: huubvandemortel, at: 05/31/2007 09:49

  • #2
    Re:What to do with ERROR status

    Are you using 1.5?
    Chris Lang

    Comment


    • #3
      Re:What to do with ERROR status

      Yes

      Comment


      • #4
        Re:What to do with ERROR status

        How large are your messages? Is this a fresh install of 1.5 and are you using Derby or Postgres as the db?

        You can prevent queueing by turning off "use persistent queues" on the LLP sender.
        Chris Lang

        Comment


        • #5
          Re:What to do with ERROR status

          yes this is a fresh 1.5 install with imported channels. I'm using derby and the messages are small ADT-messages.
          The query on the database is continuously. On 7000 Received messages on the source connector I have 20 errors by now.

          I'm a little confused by the functionality of the Reprocess Action. I would expect that the Error is reprocessed on the destination it failed. On the dashboard I see the received counter incremented as wel as the sent counter. I would expect onlu the sent counter to be incremented because no new messages is received on the source connecter.

          I would als expect the error counter to decrement because an ERROR mesaage was retransmitted and th error situation was solved.

          I guess to keep track of all Error situations I need Persistent Queue to be ON.

          Post edited by: huubvandemortel, at: 06/04/2007 01:13

          Comment


          • #6
            Re:What to do with ERROR status

            When you reprocess a message, it sends it through the entire channel - it will show up as a received and sent. It will also not update the error status. You will have to clear these manually.

            You do not need to leave queuing on for errors to be reported/reprocessed. Without the queue, the errored messages still appear in the message browser and can be reprocessed.
            Chris Lang

            Comment

            Working...
            X