Details

    • Type: Bug Bug
    • Status: Ready for QA Ready for QA (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: FN
    • Labels:
    • Customer:
      OMAN-Tel

      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>

        Activity

        Hide
        Zein Trabelsi added a comment -

        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.

        Show
        Zein Trabelsi added a comment - 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.

          People

          • Assignee:
            Mbaye Lo
            Reporter:
            Mbaye Lo
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:

              Drag and Drop