ACE
  1. ACE
  2. ACE-695

FetchGisInfo SRD API is failing : The host did not accept the connection within timeout of 60000 ms

    Details

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

      Description

      FetchGisInfo SRD API is failing : The host did not accept the connection within timeout of 60000 ms

      Request:
      <SOAP-ENV:Envelope
      xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP-ENV:Header/>
      <SOAP-ENV:Body>
      <ns3:fetchGisInfo
      xmlns:ns3="http://server.internal.api.srd.nep.mobinets.com/"
      xmlns="">
      <inputParameter>682631,2590222</inputParameter>
      <directSave>false</directSave>
      <requestId>02102024</requestId>
      <serviceName>1094301_FBB</serviceName>
      <siteName></siteName>
      <siteType></siteType>
      </ns3:fetchGisInfo>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      Response :
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <soap:Fault>
      <faultcode>soap:Server</faultcode>
      <faultstring>The host did not accept the connection within timeout of 60000 ms</faultstring>
      <detail>
      <ns1:Exception xmlns:ns1="http://server.internal.api.srd.nep.mobinets.com/"/>
      </detail>
      </soap:Fault>
      </soap:Body>
      </soap:Envelope>

        Activity

        Hide
        Ayed Bada added a comment -

        Dear Mbaye,

        We are currently facing an issue while invoking the GIS service endpoint:

        https://geoservice.omantel.om/OBCP/OBC.svc

        During execution of the method fetchGisInfo, the request fails with a timeout exception. Please find the relevant logs below:

        ERROR during service call:
        Unable to sendViaPost to url https://geoservice.omantel.om/OBCP/OBC.svc
        org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 60000 ms

        This indicates that the connection to the endpoint could not be established within the configured timeout period.

        Could you please check with the Integration team and confirm the following points:

        -Whether access to this service requires a VPN connection or a Public IP
        -If there is an internal endpoint that should be used when connected via VPN
        -The expected access configuration to ensure successful connectivity

        Best regards,

        Show
        Ayed Bada added a comment - Dear Mbaye, We are currently facing an issue while invoking the GIS service endpoint: https://geoservice.omantel.om/OBCP/OBC.svc During execution of the method fetchGisInfo, the request fails with a timeout exception. Please find the relevant logs below: ERROR during service call: Unable to sendViaPost to url https://geoservice.omantel.om/OBCP/OBC.svc org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 60000 ms This indicates that the connection to the endpoint could not be established within the configured timeout period. Could you please check with the Integration team and confirm the following points: -Whether access to this service requires a VPN connection or a Public IP -If there is an internal endpoint that should be used when connected via VPN -The expected access configuration to ensure successful connectivity Best regards,
        Hide
        Mbaye Lo added a comment - - edited

        API : fetchGisInfo
        Please support to prepare the input of this API as the current one is showing Location details not correct on Staging and on .84, response is empty

        <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
        <SOAP-ENV:Header/>
        <SOAP-ENV:Body>
        <ns3:fetchGisInfo
        xmlns:ns3="http://server.internal.api.srd.nep.mobinets.com/"
        xmlns="">
        <inputParameter>57.79446861133316,23.726978242090063</inputParameter>
        <directSave>false</directSave>
        <requestId>2040</requestId>
        <serviceName>1095548_FBB</serviceName>
        <siteName>MC1 Barka</siteName>
        <siteType>A</siteType>
        </ns3:fetchGisInfo>
        </SOAP-ENV:Body>
        </SOAP-ENV:Envelope>

        <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
        <soap:Body>
        <ns2:fetchGisInfoResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">
        <return>
        <returnMessage>Please enter valid location. Long,lat</returnMessage>
        </return>
        </ns2:fetchGisInfoResponse>
        </soap:Body>
        </soap:Envelope>

        Show
        Mbaye Lo added a comment - - edited API : fetchGisInfo Please support to prepare the input of this API as the current one is showing Location details not correct on Staging and on .84, response is empty <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:fetchGisInfo xmlns:ns3="http://server.internal.api.srd.nep.mobinets.com/" xmlns=""> <inputParameter>57.79446861133316,23.726978242090063</inputParameter> <directSave>false</directSave> <requestId>2040</requestId> <serviceName>1095548_FBB</serviceName> <siteName>MC1 Barka</siteName> <siteType>A</siteType> </ns3:fetchGisInfo> </SOAP-ENV:Body> </SOAP-ENV:Envelope> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:fetchGisInfoResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/"> <return> <returnMessage>Please enter valid location. Long,lat</returnMessage> </return> </ns2:fetchGisInfoResponse> </soap:Body> </soap:Envelope>
        Hide
        Zein Trabelsi added a comment -

        The problem is not how to construct the request, your request is valid but as Ayed respond : this API internally calls an external OBC GIS service at https://geoservice.omantel.om/OBCP/OBC.svc to fetch the GIS information, and this external service is not accessible from server 84 (connection timeout after 60s). This is a network/infrastructure issue, the network team needs to open outbound HTTPS access from server 84 to geoservice.omantel.om:443.

        Show
        Zein Trabelsi added a comment - The problem is not how to construct the request, your request is valid but as Ayed respond : this API internally calls an external OBC GIS service at https://geoservice.omantel.om/OBCP/OBC.svc to fetch the GIS information, and this external service is not accessible from server 84 (connection timeout after 60s). This is a network/infrastructure issue, the network team needs to open outbound HTTPS access from server 84 to geoservice.omantel.om:443.
        Hide
        Mbaye Lo added a comment - - edited

        I reopened it because the test is failing on the Staging .179, it's showing "Location details not correct", I tried 2 coordinate formats : 

         

        Lat/Long, EST/WEST. For the timeout response on .84, I asked Natnael to check. 

        <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
        <soap:Body>
        <ns2:fetchGisInfoResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">
        <return>
        <returnMessage>Please enter valid location. Long,lat</returnMessage>
        </return>
        </ns2:fetchGisInfoResponse>
        </soap:Body>
        </soap:Envelope>

        Show
        Mbaye Lo added a comment - - edited I reopened it because the test is failing on the Staging .179, it's showing "Location details not correct", I tried 2 coordinate formats :    Lat/Long, EST/WEST. For the timeout response on .84, I asked Natnael to check.  <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:fetchGisInfoResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/"> <return> <returnMessage>Please enter valid location. Long,lat</returnMessage> </return> </ns2:fetchGisInfoResponse> </soap:Body> </soap:Envelope>

          People

          • Assignee:
            Mbaye Lo
            Reporter:
            Mbaye Lo
            Rejected By:
            Zein Trabelsi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

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

              Drag and Drop