Announcement

Collapse
No announcement yet.

Database writer queuing issue

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

  • Database writer queuing issue

    I'm trying to queue message for sometime before it move to error .
    My understanding is that if there is any SQL level exception like Duplicate Primary Key or other SQL issues, then mirth should re-try for 3 times until then it will be queued.
    More than the third time it should automatically go to the error queue.

    But what is happening is, when I get duplicate primary key it is going to queue only and not to error. I have given queue always, and have below code for retrying

    Code:
    if (responseStatus == QUEUED && connectorMessage.getSendAttempts() >=3) {
            responseStatus = ERROR;
    }
    This is my DB writer destination configuration. Can anyone help?

    Mirth Interface Engineer
    AWS DevOps

  • #2
    Try setting your response data types to Raw so that the response transformer will always execute even if there's no response.
    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

    Working...
    X