[ACE-694] checkMwOrGeFeasibility SRD API is failing Created: 06/Mar/26  Updated: 08/Jun/26  Due: 03/Mar/26  Resolved: 02/Jun/26

Status: Ready for QA
Project: ACE
Component/s: SRD
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Mbaye Lo Assignee: Mbaye Lo
Resolution: Not Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Untitled.png    
Issue Links:
Cloners
is cloned by ACE-962 While completing the HBB order from F... Rejected
Customer:
OMAN-Tel
Planned Start:
Planned End:
Rejected By: Zein Trabelsi

 Description   

checkMwOrGeFeasibility API is failing

Request :
<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:checkMwOrGeFeasibility>
<!-Optional:->
<requestId>821</requestId>
<!-Optional:->
<serviceName>1319442_FBB</serviceName>
<!-Optional:->
<siteLat>23.55626893321905</siteLat>
<!-Optional:->
<siteLong>58.21754375406719</siteLong>
<!-Optional:->
<maxDistanceInMeters>30.0</maxDistanceInMeters>
<!-Optional:->
<coordinateFormat>geo_wgs84</coordinateFormat>
<!-Optional:->
<bandWith>10</bandWith>
<!-Optional:->
<nbLines>10</nbLines>
<!-Optional:->
<nbChannels>10</nbChannels>
</ser:checkMwOrGeFeasibility>
</soapenv:Body>
</soapenv:Envelope>

Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>eq(null) is not allowed. Use isNull() instead</faultstring>
<detail>
<ns1:NepFault xmlns:ns1="http://server.internal.api.srd.nep.mobinets.com/">
<errorCode xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">-1</errorCode>
</ns1:NepFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>



 Comments   
Comment by Zein Trabelsi [ 10/Mar/26 ]

check if customer name is null before using eq method of QueryDSL

Comment by Zein Trabelsi [ 10/Mar/26 ]

fix will be available with release 4.0.0.5

Comment by Mbaye Lo [ 18/May/26 ]

API : checkMwOrGeFeasibility
Please support to prepare the input of this API as the current one is showing error

<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:checkMwOrGeFeasibility>
<!-Optional:->
<requestId>821</requestId>
<!-Optional:->
<serviceName>1319442_FBB</serviceName>
<!-Optional:->
<siteLat>23.55626893321905</siteLat>
<!-Optional:->
<siteLong>58.21754375406719</siteLong>
<!-Optional:->
<maxDistanceInMeters>30.0</maxDistanceInMeters>
<!-Optional:->
<coordinateFormat>geo_wgs84</coordinateFormat>
<!-Optional:->
<bandWith>10</bandWith>
<!-Optional:->

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>eq(null) is not allowed. Use isNull() instead</faultstring>
<detail>
<ns1:NepFault xmlns:ns1="http://server.internal.api.srd.nep.mobinets.com/">
<errorCode xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">-1</errorCode>
</ns1:NepFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
<nbLines>10</nbLines>
<!-Optional:->
<nbChannels>10</nbChannels>
</ser:checkMwOrGeFeasibility>
</soapenv:Body>
</soapenv:Envelope>

Comment by Zein Trabelsi [ 20/May/26 ]

it works try below request :

<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:checkMwOrGeFeasibility>
<requestId>646</requestId>
<serviceName>1291106_MPLS</serviceName>
<siteLat>19.529411</siteLat>
<siteLong>57.6157</siteLong>
<maxDistanceInMeters>50000</maxDistanceInMeters>
<coordinateFormat>geo_wgs84</coordinateFormat>
<bandWith>10</bandWith>
<nbLines>1</nbLines>
<nbChannels>1</nbChannels>
</ser:checkMwOrGeFeasibility>
</soapenv:Body>
</soapenv:Envelope>

Comment by Mbaye Lo [ 20/May/26 ]

Working, but getting Performance issue now : 1.2s versus 21s

Comment by Mbaye Lo [ 02/Jun/26 ]

Perf Issue

Comment by Ayed Bada [ 03/Jun/26 ]

Implemented a performance improvement by fetching data directly from the database instead of using the report layer.

This change is included in patch version *4.0.0.8*.

Generated at Mon Jun 15 15:19:19 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.