[ACE-573] WorkOrder Copper NewActivation is created but with performance issue, Created: 13/Feb/26  Updated: 13/Feb/26  Due: 12/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   

WorkOrder Copper NewActivation is created but with performance issue, more more than 300 secondes on FN-NEW compared to compared to 13 secondes on the OLD.

The response on the OLD, also, the response is still showing :

".UnexpectedRollbackException: Transaction silently rolled back because it has been marked as rollback-only"

It should be "0". T

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:arborSingleWO_fCNA>
<fAppType>I</fAppType>
<fExc>QUR2</fExc>
<fCabinet>001</fCabinet>
<fDpoint>0008</fDpoint>
<fSubno>44440092</fSubno>
<fSubscr_Type>T</fSubscr_Type>
<fWOID>4444000292</fWOID>
<fUsage_Type>2</fUsage_Type>
<fOrder_Type>INST</fOrder_Type>
<fUserID>96109</fUserID>
<arborOrderId>444400092</arborOrderId>
</ser:arborSingleWO_fCNA>
</soapenv:Body>
</soapenv:Envelope>

FN / OLD
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>org.springframework.transaction.UnexpectedRollbackException: Transaction silently rolled back because it has been marked as rollback-only</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

FN / NEW
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-c7887bbd-bd63-4df7-83e6-8888e0e99448">
<wsse:Username>nep-api-key</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">mobinets@2017</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<soap:Body>
<ns2:arborSingleWO_fCNAResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>0</return>
</ns2:arborSingleWO_fCNAResponse>
</soap:Body>
</soap:Envelope>



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

Root cause: getFfmsWorkOrderDetails calls isVDSLFeasible, which previously depended on the slow view FN_CONNECTION_AVAILABILITY_V.
This resulted in long execution times. The method has been refactored to OspConnection table directly.

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