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:
      None Labels
    • Customer:
      OMAN-Tel

      Description

      API checkRequestNewActivationFeasibility has performance issue :

      2s in the OLD versus 4s in the NEW

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

      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <ns2:checkRequestNewActivationFeasibilityResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
      <return>
      <exc>QUR2</exc>
      <request xmlID="iD">
      <id>NETWORKFC1099267</id>
      <changedate>2026-02-23T13:31:44+04:00</changedate>
      <changedby>NEP</changedby>
      <insertdate>2021-07-07T14:18:17+04:00</insertdate>
      <customerType>CONSUMER</customerType>
      <errorCode>0</errorCode>
      <migratedRequest>true</migratedRequest>
      <networkType>GPON</networkType>
      <numCount>6</numCount>
      <pendAreaClass>GREEN</pendAreaClass>
      <ports>TRUE</ports>
      <remarks>No Remarks</remarks>
      <requestNo>526484</requestNo>
      <requestType>New PSTN + Data</requestType>
      <scn>3</scn>
      <serviceType>GPON VOICE AND DATA HP1</serviceType>
      <dType>REQUEST</dType>
      </request>
      <responseCode>0</responseCode>
      <responseMessage>SUCCESS</responseMessage>
      <trails>
      <id>ServiceTrailDto_-226975</id>
      <changedate>2026-02-23T13:32:06+04:00</changedate>
      <changedby>System</changedby>
      <insertBy>NEP</insertBy>

        Activity

        Hide
        Zein Trabelsi added a comment -

        Fixed in last release :
        by adding index in Request table & enhancing the ospconnection retrieving using union all instead of complicated where in clause .
        I have tested the request in both it takes 2.5 in new and 2.1 in old . and thats normal and we couldnt classify it as performance issue (difference of milliseconds)

        Show
        Zein Trabelsi added a comment - Fixed in last release : by adding index in Request table & enhancing the ospconnection retrieving using union all instead of complicated where in clause . I have tested the request in both it takes 2.5 in new and 2.1 in old . and thats normal and we couldnt classify it as performance issue (difference of milliseconds)

          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