ACE
  1. ACE
  2. ACE-716

Review SRD API checkCopperTrailFeasibility

        Details

        • Type: Bug Bug
        • Status: Ready for QA Ready for QA (View Workflow)
        • Priority: Normal Normal
        • Resolution: Unresolved
        • Affects Version/s: None
        • Fix Version/s: None
        • Component/s: SRD
        • Labels:
        • Customer:
          OMAN-Tel

          Description

          Review SRD API checkCopperTrailFeasibility :

          <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/">
          <soapenv:Header/>
          <soapenv:Body>
          <ser:checkCopperTrailFeasibility>
          <!-Optional:->
          <requestId>12082024</requestId>
          <!-Optional:->
          <siteLat>23.55626893321905</siteLat>
          <!-Optional:->
          <siteLong>58.21754375406719</siteLong>
          <!-Optional:->
          <maxDpDistanceInMeters>1000</maxDpDistanceInMeters>
          <!-Optional:->
          <maxExchangeDistanceInMeters>1000</maxExchangeDistanceInMeters>
          <!-Optional:->
          <coordinateFormat>EAST_NORTH</coordinateFormat>
          <!-Optional:->
          <serviceTypeName>New</serviceTypeName>
          <!-Optional:->
          <dataProfilType>?</dataProfilType>
          <!-Optional:->
          <bandWith>100.0</bandWith>
          <!-Optional:->
          <nbLines>100.0</nbLines>
          <!-Optional:->
          <nbChannels>100.0</nbChannels>
          </ser:checkCopperTrailFeasibility>
          </soapenv:Body>
          </soapenv:Envelope>

            Activity

            Hide
            Permalink
            Ayed Bada added a comment -

            I checked the logs and found that the API returns <responseMessage>No Trail found</responseMessage> because the NEP API returned null.
            I retested the use case locally, and the NEP API returned correct data for ID 84. This suggests that the issue may occur when the NEP service is down, causing checkCopperTrailFeasibility to return an invalid response.
            Currently, the VPN is down, so I cannot verify whether the API is returning valid data in that environment.
            In another case, the API returns <responseMessage>SRD_DP_MVIEW</responseMessage>. This occurs because the SRD backend reads from a materialized view instead of the correct view.
            Fixed the HttpClientErrorException issue.

            This issue will be resolved in patch 4.0.0.5.

            Show
            Ayed Bada added a comment - I checked the logs and found that the API returns <responseMessage>No Trail found</responseMessage> because the NEP API returned null. I retested the use case locally, and the NEP API returned correct data for ID 84. This suggests that the issue may occur when the NEP service is down, causing checkCopperTrailFeasibility to return an invalid response. Currently, the VPN is down, so I cannot verify whether the API is returning valid data in that environment. In another case, the API returns <responseMessage>SRD_DP_MVIEW</responseMessage>. This occurs because the SRD backend reads from a materialized view instead of the correct view. Fixed the HttpClientErrorException issue. This issue will be resolved in patch 4.0.0.5.
            Cancel

              People

              • Assignee:
                Mbaye Lo
                Reporter:
                Mbaye Lo
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Planned Start:
                  Planned End:

                  Drag and Drop