http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/ACE-716 ACE <p>Review SRD API checkCopperTrailFeasibility : </p> <p>&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/"&gt;<br/> &lt;soapenv:Header/&gt;<br/> &lt;soapenv:Body&gt;<br/> &lt;ser:checkCopperTrailFeasibility&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;requestId&gt;12082024&lt;/requestId&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;siteLat&gt;23.55626893321905&lt;/siteLat&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;siteLong&gt;58.21754375406719&lt;/siteLong&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;maxDpDistanceInMeters&gt;1000&lt;/maxDpDistanceInMeters&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;maxExchangeDistanceInMeters&gt;1000&lt;/maxExchangeDistanceInMeters&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;coordinateFormat&gt;EAST_NORTH&lt;/coordinateFormat&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;serviceTypeName&gt;New&lt;/serviceTypeName&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;dataProfilType&gt;?&lt;/dataProfilType&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;bandWith&gt;100.0&lt;/bandWith&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;nbLines&gt;100.0&lt;/nbLines&gt;<br/> &lt;!-<del>Optional:</del>-&gt;<br/> &lt;nbChannels&gt;100.0&lt;/nbChannels&gt;<br/> &lt;/ser:checkCopperTrailFeasibility&gt;<br/> &lt;/soapenv:Body&gt;<br/> &lt;/soapenv:Envelope&gt;</p> ACE-716

Review SRD API checkCopperTrailFeasibility

Bug Normal Ready for QA Unresolved Mbaye Lo Mbaye Lo Milestone2 Tue, 10 Mar 2026 06:37:15 +0200 Thu, 2 Apr 2026 08:52:40 +0300 SRD Tue, 10 Mar 2026 00:00:00 +0200 0 2 <p>I checked the logs and found that the API returns &lt;responseMessage&gt;No Trail found&lt;/responseMessage&gt; because the NEP API returned null.<br/> 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.<br/> Currently, the VPN is down, so I cannot verify whether the API is returning valid data in that environment.<br/> In another case, the API returns &lt;responseMessage&gt;SRD_DP_MVIEW&lt;/responseMessage&gt;. This occurs because the SRD backend reads from a materialized view instead of the correct view.<br/> Fixed the HttpClientErrorException issue.</p> <p>This issue will be resolved in patch 4.0.0.5.</p> Customer Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Tue, 10 Mar 2026 00:00:00 +0200 Planned Start Tue, 10 Mar 2026 00:00:00 +0200 Rank 0|xtiyq1: Rank (Obsolete) 9223372036854775807 VTDirections