No announcement yet.

SOAP error

  • Filter
  • Time
  • Show
Clear All
new posts

  • SOAP error

    Hello has anyone else encountered this error before or know how I can fix it?

    Here is the error:

    [2013-09-24 11:15:16,757] ERROR (Server:146): Sep 24, 2013 11:15:16 AM fill
    [2013-09-24 11:15:16,773] ERROR (Server:146): WARNING: BindingProvider.SOAPACTION_URI_PROPERTY is set in the RequestContext but is ineffective, Either set BindingProvider.SOAPACTION_USE_PROPERTY to true or enable AddressingFeature

    I am using Mirth Connect This process is working, but it is spamming my Mirth console log with the error. I am querying our state registry for immunization records and they send me a respose to the query. The query and message are in HL7 format but they are embedded in a SOAP envelope. I am using Mirths embedded web service sender to embed the HL7 message in a SOAP envelope and send the query.

    <soap:Envelope xmlns:soap="" xmlns:tem="">

    When I receive the response I am using this javascript statement to extract the HL7 messages from the soap envelope.

    var soap = new Namespace('');
    var tempuri = new Namespace('');

    tmp = new XML(SerializerFactory.getHL7Serializer().toXML(msg .soap::Body.tempuri::ExecuteHL7MessageResponse.tem puri::ExecuteHL7MessageResult.toString()));

    Here is an example of a response message from the state with the HL7 message removed for PHI reasons.

    SUCCESS: <?xml version="1.0" encoding="UTF-8" standalone="no"?><soap:Envelope xmlns:soap="" xmlns:xsd="" xmlns:xsi=""><soap:Header/><soap:Body><ExecuteHL7MessageResponse xmlns=""><ExecuteHL7MessageResult>
    HL7 Removed here.

    This error make sense to anyone?

  • #2
    That may be related to MIRTH-2109, fixed in 2.2.2 and 3.0.
    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.


    • #3
      Thanks Narupley! I have the upgrade to 2.2.3 on my to do list in the next month. Just waiting on an HIS upgrade to happen in the next few weeks before I change anything with Mirth.