[ACE-596] checkRequestNewActivationFeasibility has Performance Issue Created: 19/Feb/26  Updated: 26/Feb/26  Due: 18/Feb/26  Resolved: 26/Feb/26

Status: Closed
Project: ACE
Component/s: FN
Affects Version/s: None
Fix Version/s: None

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

Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

checkRequestNewActivationFeasibility has Performance Issue : 2s versus 5s

<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>

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

add index on Request table by request_no + use query dsl eq method instead equalsIgnoreCase.
add index in service_trail_hop by OSP_CONNECTION, SERVICE_TRAIL_ID + remove lower(status.NAME) when fetching ospconnections .

these changes would decrease response time from 5 to 2 s

Comment by Mbaye Lo [ 26/Feb/26 ]

Fixed

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