[ACE-587] API CancellOrder has Perfonfmance issue Created: 18/Feb/26  Updated: 23/Feb/26  Due: 18/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: Milestone2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

API CancellOrder has Perfonfmance issue :

ON OLD : 21s
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:cancelOrder>
<!-Optional:->
<woNo>4444000293</woNo>
<!-Optional:->
<cancellationCode>SUBR</cancellationCode>
<!-Optional:->
<cancellationReason>UBO</cancellationReason>
</ser:cancelOrder>
</soapenv:Body>
</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:cancelOrderResponse xmlns:ns2="http://server.api.nep.mobinets.com/"/>
</soap:Body>
</soap:Envelope>

ON NEW : 79s
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:cancelOrder>
<!-Optional:->
<woNo>444400151</woNo>
<cancellationCode>SUBR</cancellationCode>
<!-Optional:->
<cancellationReason>UBO</cancellationReason>
</ser:cancelOrder>
</soapenv:Body>
</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:cancelOrderResponse xmlns:ns2="http://server.api.nep.mobinets.com/"/>
</soap:Body>
</soap:Envelope>



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

We are working on it, to ignore flowable database access the main part causing the performance issue

Comment by Zein Trabelsi [ 23/Feb/26 ]

instead of retrieving task id from flowable database (any time we need to complete a task) , we store this information in new tabe in our database when create the task , and remove the record after completion.

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