Uploaded image for project: 'XDStarClient'
  1. XDStarClient
  2. XDSTAR-668

(Continued) Issues on reporting the result of XCPD ITI-55 transaction when initiating from the tool

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2018 - S2, 2018 - S1, 2018 - S3
    • Account:
      The Hague 2018 (EUCAT2018)

      Description

      In XDSTAR-571 Anne-Gaelle Berge reported the following symptoms:

      {quote}
      The tool fails in sending a request to Patient Manager XCPD Responding Gateway with the message:
      The request has not be sent to the server. An exception occure when trying to send the request : java.io.IOException: java.lang.NullPointerException
          at net.ihe.gazelle.xdstar.comon.util.URLCheck.createHttpsConnection(URLCheck.java:93)
          at net.ihe.gazelle.xdstar.comon.util.URLCheck.createHttpsConnection(URLCheck.java:62)
          at net.ihe.gazelle.xdstar.core.MessageSenderCommon.sendOverHttps(MessageS...

      This message is reported as the response message in the execution summary.
      Three issues here:
      * A null pointer exception is raised
      * the response is said to be PRPA_IN201306UV02 whereas no response was really received (so it is hard coded and if the SUT answers with another message type it will not show up here which is an issue)
      * I asked for validation and the status for the response (a stack trace in our case) is PASSED whereas the validation report shows a failure (I would not send to the validator a message which is not an XML string)

      http://sake.irisa.fr/XDStarClient//messages/message.seam?id=18313

      Note that it is working when I use a non TLS endpoint.
      {quote}

      This was reportedly fixed in XDSTAR-626, incorporated in the 2.1.1 build of XDStar which I show is the currently in-use build on https://gazelle.ihe.net/XDStarClient/home.seam by clicking on "About" at the bottom of the page.

      However, I'm experiencing an identical issue. There were some open questions on XDSTAR-517 that may be in play here:

      {quote}
      does the fix also takes into account those remarks:

      * A null pointer exception is raised
      * the response is said to be PRPA_IN201306UV02 whereas no response was really received (so it is hard coded and if the SUT answers with another message type it will not show up here which is an issue)
      * I asked for validation and the status for the response (a stack trace in our case) is PASSED whereas the validation report shows a failure (I would not send to the validator a message which is not an XML string)
      otherwise I will create another issue because I think that the consistency is very important for users
      {quote}

      My issue:

      I'm a logged-in user (username: johnhd) on https://gazelle.ihe.net/XDStarClient/cas/home.seam

      I created a XCPD Responding Gateway under *SUT Configurations > XCPD Responding Gateway Configuration* named *Zen Stargate Test*. (I have made it public for your review)

      (I will attach an image as well if I can figure out how on this version of JIRA)

      I then navigate to *SIMU-Initiators > IHE [ITI] > XCPD > ITI-55*

      I select "Zen Stargate Test" from the dropdown, leave the default values in-place and simply click "Execute".

      https://gazelle.ihe.net/XDStarClient//messages/message.seam?id=18629

      I obtain the same results as XDSTAR-571:
      {code}
      The request has not be sent to the server. An exception occure when trying to send the request : java.io.IOException: java.lang.NullPointerException
          at net.ihe.gazelle.xdstar.comon.util.URLCheck.createHttpsConnection(URLCheck.java:93)
          at net.ihe.gazelle.xdstar.comon.util.URLCheck.createHttpsConnection(URLCheck.java:62)
          at net.ihe.gazelle.xdstar.core.MessageSenderCommon.sendOverHttps(MessageS...
      {code}

      I perform a packet capture on my server side and see 0 packets as well, strongly suggesting that the issue exists on the client (Gazelle XDStar) side and is occurring prior to the connection attempt.

      I also spot checked this same workflow against several other public configurations and received the same result including:

      * CZECH_NCP_A
      ** https://gazelle.ihe.net/XDStarClient//messages/message.seam?id=18631
      * epSOS Simulator Secured
      ** https://gazelle.ihe.net/XDStarClient//messages/message.seam?id=18632

      *NOTE:* As a point of comparison, I also tried *epSOS SImulator Unsecured* and retrieved an apparent successful response!

      https://gazelle.ihe.net/XDStarClient//messages/message.seam?id=18628

      (I tried to look up other likely partners by looking for recent successes under *Messages > Simulator as Initiator > Filter on "Transaction" of ITI-55 & Sort by ResponseCode*, looking for ResponseCodes of 200.

      Most of these are for a partner labelled "IHE_EUROPE" which I'm assuming is private; I cannot find it under "Cross Gateway Patient Discovery" to test against. )

      Taken together, I suspect there is some issue related to whether a partner gateway is secured (HTTPS) or not (HTTP).

      I'm happy to provide any additional information I can to help diagnose this issue.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hra Hilary Rabe
                Reporter:
                johnhd John Henry Downing
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 7 hours, 30 minutes
                  7h 30m

                    Potential Duplicates