[ACE-629] updateOldResourcesStatus has performance issue Created: 03/Mar/26  Updated: 09/Mar/26  Due: 03/Mar/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   

updateOldResourcesStatus has performance issue

4s in new 1.5s in old

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:updateOldResourcesStatus>
<!-Optional:->
<subscriberNo>25796019</subscriberNo>
<!-Optional:->
<status>spare</status>
</ser:updateOldResourcesStatus>
</soapenv:Body>
</soapenv:Envelope>



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

changed the logic of finding ospconnection related to fn_service_trail_hop (FnInternalService.getOspConnection (TransferredOspConnection)) .
we have change the logic of this method (create two new methods in same class with same name and different params) .
instead of for each hop retrieve node1+node2 + retrieving all ospconnections by node1id and node2id then for each connection get the transferred object and check if port1key = port2key (we may have hundreds connections between two nodes) ==> fetching the related node1 + node2 (By nodeName and nodeType) and port1 + port2 (By NeId and portKey) then fetch directly the related ospconnection (only one match)

Comment by Zein Trabelsi [ 09/Mar/26 ]

it takes now 1s :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:updateOldResourcesStatus>
<!-Optional:->
<subscriberNo>25796019</subscriberNo>
<!-Optional:->
<status>Working pair</status>
</ser:updateOldResourcesStatus>
</soapenv:Body>
</soapenv:Envelope>

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