Details
-
Type:
Bug
-
Status:
Ready for QA
(View Workflow)
-
Priority:
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
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2026-03-10 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2026-03-10 24:00 (milestone: set planned end date to due date) |
| Assignee | Zein Trabelsi [ ztrabelsi ] | Ayed Bada [ abada ] |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Ayed Bada [ abada ] | Mbaye Lo [ mbayel ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
22d 6h 19m | 1 | Ayed Bada | 01/Apr/26 1:56 PM | |||||
|
6s | 1 | Ayed Bada | 01/Apr/26 1:56 PM | |||||
|
1h 30m | 1 | Ayed Bada | 01/Apr/26 3:27 PM | |||||
|
17h 24m | 1 | Khaled Khalil | 02/Apr/26 8:52 AM |
|
Links Hierarchy |
 Documentation
|
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.