Announcement

Collapse
No announcement yet.

502 error with Channel Writer

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

  • 502 error with Channel Writer

    We are seeing an occasional 502 error

    "Wrapped java.io.IOException: Server returned HTTP response code: 502 for URL: http://localhost/InterfaceEngine/api/MeditechAdtToCbordOut/Transform?connectorId=15&channelId=79826d24-b952-46d5-b864-c307b5ee6775"

    This channel typically sends thousands of messages daily and only a few have this error on any given day.

    Can anyone shed some light on what might cause the error? The writer and reader are on the same machine (as is the database.) Initial thought was "Bad Gateway" but why would that happen if everything is on the same machine? Would the channel reader (receiving end that sends to a remote PC) be causing the error in the channel writer?

  • #2
    The 502 Bad Gateway error is an HTTP status code that means that one server on the internet received an invalid response from another server.

    It just means that you have lost connection some where along the line. They should go through if you reprocess them.

    If that works, you can write an alert that will automatically reprocess them.

    Comment


    • #3
      Channel Writers/Readers don't communicate with HTTP. Are you sure they aren't set up as HTTP Sender/Listeners?

      Comment


      • #4
        Yes these are a Channel Writer to a Channel Reader. That is why I was wondering if the Channel Reader which sends to an outside PC as a destination is where the error is actually happening.

        Comment


        • #5
          On your channel reader, under source-response what do you have selected?

          Comment


          • #6
            In the Channel Reader:
            Source Queue: ON (Respond before processing)
            Queue Buffer Size: 1000
            Response: None
            Process Batch: No
            Max Processing Threads 1

            Comment


            • #7
              Are you on a mirth version earlier than 3.0?

              Comment


              • #8
                We are running version 3.6.1.

                Comment


                • #9
                  Look at your transformer/filter to see if there is anything in there using HTTP.

                  Comment


                  • #10
                    Are you able to export and attach your channels for us to look at?

                    Comment


                    • #11
                      The other developers want to wait. We are submitting a message within our application to the Mirth API and they feel it might be the cause of the error. So right now I will add error checking in our code to see if that sheds any light.

                      Comment

                      Working...
                      X