[ACE-602] API checkRequestNewActivationFeasibility has performance issue Created: 23/Feb/26  Updated: 25/Feb/26  Due: 23/Feb/26

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

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

Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

API checkRequestNewActivationFeasibility has performance issue :

2s in the OLD versus 4s in the NEW

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:checkRequestNewActivationFeasibility>
<!-Optional:->
<requestId>526484</requestId>
</ser:checkRequestNewActivationFeasibility>
</soapenv:Body>
</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:checkRequestNewActivationFeasibilityResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>
<exc>QUR2</exc>
<request xmlID="iD">
<id>NETWORKFC1099267</id>
<changedate>2026-02-23T13:31:44+04:00</changedate>
<changedby>NEP</changedby>
<insertdate>2021-07-07T14:18:17+04:00</insertdate>
<customerType>CONSUMER</customerType>
<errorCode>0</errorCode>
<migratedRequest>true</migratedRequest>
<networkType>GPON</networkType>
<numCount>6</numCount>
<pendAreaClass>GREEN</pendAreaClass>
<ports>TRUE</ports>
<remarks>No Remarks</remarks>
<requestNo>526484</requestNo>
<requestType>New PSTN + Data</requestType>
<scn>3</scn>
<serviceType>GPON VOICE AND DATA HP1</serviceType>
<dType>REQUEST</dType>
</request>
<responseCode>0</responseCode>
<responseMessage>SUCCESS</responseMessage>
<trails>
<id>ServiceTrailDto_-226975</id>
<changedate>2026-02-23T13:32:06+04:00</changedate>
<changedby>System</changedby>
<insertBy>NEP</insertBy>



 Comments   
Comment by Zein Trabelsi [ 25/Feb/26 ]

Fixed in last release :
by adding index in Request table & enhancing the ospconnection retrieving using union all instead of complicated where in clause .
I have tested the request in both it takes 2.5 in new and 2.1 in old . and thats normal and we couldnt classify it as performance issue (difference of milliseconds)

Generated at Wed Apr 15 09:16:12 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.