No announcement yet.

Axis timeout on Mirth in Linux

  • Filter
  • Time
  • Show
Clear All
new posts

  • Axis timeout on Mirth in Linux

    Hello all.

    I have made progress on my plugin, but to test the core of what I want I wrote it up in a jar that is being run from a javascript channel.

    This is connecting to a remote server using Axis/JaxRPC/SOAP

    The code runs in Windows and from the command line in both windows and linux, However it is not working in Linux when run from inside of Mirth.

    I moved the jar over to linux, I put it in the mirth lib directory
    And I can run it from the command line without issue. When a channel uses the code it throws a read timeout exception

            {}stackTrace:Internal Error: unable to process your request: javax.xml.soap.SOAPException: Unable to instantiate the stream, the error was: Read timed out
    I am a bit confused by this, I have tried adding an explicit timeout (up to 30 seconds, using setTimeout in the axis stub) with no success. The remote calls execute almost immediately when run from the command line on the linux machine. Any ideas here?

    Java version in Linux : Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
    Java version in Windows : Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
    Mirth version is 1.8.0 on both

  • #2
    I solved the problem, but it raises a question.

    The problem was the file client-config.wsdd in the /conf directory. That file is not there for instances of Mirth that used an installer, however it is there in instances that were from the tar.gz and zip files.

    Removing this file solved the timeout problem (which, it turns out, happens in Windows if you used a zip install), but I am confused as to why this file is not present in the installed versions. Is this file essential for anything?



    • #3
      The file is used to select the apache CommonsHTTPSender client to manage HTTP part of WS connections.

      This client supports more auth schemes than the Sun one.


      • #4
        I have always understood Send Timeout value to represent # ms to keep the connection open w/o any queued messages, then close the connection. I did not realize Mirth uses that value to wait before reopening the connection as well as best of luck for the problem is going to be solved
        Last edited by johnson33445; 11-25-2014, 02:31 AM.