Details

    • Type: Bug Bug
    • Status: Cancelled Cancelled (View Workflow)
    • Priority: Normal Normal
    • Resolution: Cannot Reproduce
    • Component/s: None
    • Labels:
    • Customer:
      OMAN-Tel

      Description

      Please explain the success response in the below log ????

      Server: .14 : archived/nep_fn_api.2025-01-07.2.log

      2025-01-07 15:10:53.942 [Thread-6] INFO c.m.t.a.EventProducer$EventConsumer - ...consuming event

      [12367326], [ARBOROBCTERM_FOBCTERM_API_ACTION]

      2025-01-07 15:11:03.079 [https-jsse-nio-8451-exec-10] INFO o.a.c.s.N.N.NepFixedNetworkService -

      Inbound Message

      ----------------------------

      ID: 24746

      Address: https://ngoss-fn-api.omantel.om/NEP_FN_API/services/fixednetworkservice

      Encoding: UTF-8

      Http-Method: POST

      Content-Type: text/xml; charset=utf-8

      Headers:

      {connection=[Keep-Alive], Content-Length=[861], content-type=[text/xml; charset=utf-8], host=[ngoss-fn-api.omantel.om], SOAPAction=["http://server.api.nep.mobinets.com/NepFixedNetworkService/arborWOREGPON_fCNAREGPON"]}

      Payload:

      <NS1:Envelope xmlns:NS1="http://schemas.xmlsoap.org/soap/envelope/">
      
          <NS1:Header>
      
              <NS2:Security
      
                  xmlns:NS2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      
                  <NS2:UsernameToken>
      
                      <NS2:Username>nep-api-key</NS2:Username>
      
                      <NS2:Password
      
                          Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
      
                          mobinets@2017</NS2:Password>
      
                  </NS2:UsernameToken>
      
              </NS2:Security>
      
          </NS1:Header>
      
          <NS1:Body>
      
              <NS3:arborWOREGPON_fCNAREGPON xmlns:NS3="http://server.api.nep.mobinets.com/">
      
                  <fAppType>I</fAppType>
      
                  <fOLT>GHA1</fOLT>
      
                  <fFDHMDU>261S</fFDHMDU>
      
                  <fDPAP>0001</fDPAP>
      
                  <fFTP>NFTP</fFTP>
      
                  <fSubscr_Type>T</fSubscr_Type>
      
                  <fWOID>1384701554A</fWOID>
      
                  <fUsage_Type>G</fUsage_Type>
      
                  <fOrder_Type>INST</fOrder_Type>
      
                  <fUserID>96441</fUserID>
      
                  <arborOrderId>263166471A</arborOrderId>
      
              </NS3:arborWOREGPON_fCNAREGPON>
      
          </NS1:Body>
      
      </NS1:Envelope>
      

      --------------------------------------

      2025-01-07 15:11:03.080 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.AuditServiceAdvice - >>>

      Start calling > arborWOREGPON_fCNAREGPON

      2025-01-07 15:11:03.080 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.OrderRequestAdvice -

      Start --> build Order Request

      2025-01-07 15:11:03.080 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.OrderRequestAdvice - End

      --> build Order Request

      2025-01-07 15:11:03.080 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.OrderRequestAdvice -

      Start --> fetching Old Record.

      2025-01-07 15:11:03.931 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.OrderRequestAdvice - End

      --> fetching Old Record.

      2025-01-07 15:11:03.931 [https-jsse-nio-8451-exec-10] INFO c.m.n.api.server.AuditServiceAdvice - >>>

      End calling > arborWOREGPON_fCNAREGPON

      2025-01-07 15:11:03.931 [https-jsse-nio-8451-exec-10] INFO o.a.c.s.N.N.NepFixedNetworkService -

      Outbound Message

      ---------------------------

      ID: 24746

      Response-Code: 200

      Encoding: UTF-8

      Content-Type: text/xml

      Headers: {}

      Payload:

      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      
          <SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      
              <wsse:Security
      
                  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"
      
                  soap:mustUnderstand="1">
      
                  <wsse:UsernameToken wsu:Id="UsernameToken-b0b66661-0d16-4931-8764-48b5d3ab7442">
      
                      <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:arborWOREGPON_fCNAREGPONResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
      
                  <return>0</return>
      
              </ns2:arborWOREGPON_fCNAREGPONResponse>
      
          </soap:Body>
      
      </soap:Envelope>
      

      Order is not created in FN neither in rejected

        Activity

        Hide
        Abir Messaikeh added a comment -

        closing for now as no new occurance are showing

        Show
        Abir Messaikeh added a comment - closing for now as no new occurance are showing
        Hide
        added a comment -

        regarding the case that found by the script, i checked logs and UI, so the order was created successfully as shown below from logs:

        create the installation order:

        Payload: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
        <SOAP-ENV:Header/>
        <SOAP-ENV:Body>
        <ns3:createWorkOrder xmlns:ns3="http://server.api.nep.mobinets.com/">
        <woNo>I1421287958</woNo>
        <arborOrderId>268710598</arborOrderId>
        <orderTypeName>20</orderTypeName>
        <subscriberNo>23279442</subscriberNo>
        <appType>SWITCHING</appType>
        <woOperation>Shifting Installation</woOperation>
        <equipementId/>
        <autoCreateTasks>false</autoCreateTasks>
        <login>96441</login>
        <exchange1>XR97</exchange1>
        <oldSubscriberNo>23234094</oldSubscriberNo>
        </ns3:createWorkOrder>
        </SOAP-ENV:Body>
        </SOAP-ENV:Envelope>

        create the termination order:

        Payload: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
        <SOAP-ENV:Header/>
        <SOAP-ENV:Body>
        <ns3:createWorkOrder xmlns:ns3="http://server.api.nep.mobinets.com/">
        <woNo>T1421287958</woNo>
        <arborOrderId>268710598</arborOrderId>
        <orderTypeName>21</orderTypeName>
        <subscriberNo>23234094</subscriberNo>
        <appType>SWITCHING</appType>
        <woOperation>Shifting Termination</woOperation>
        <equipementId/>
        <autoCreateTasks>false</autoCreateTasks>
        <login>96441</login>
        <exchange1>XR97</exchange1>
        </ns3:createWorkOrder>
        </SOAP-ENV:Body>
        </SOAP-ENV:Envelope>

        Show
        added a comment - regarding the case that found by the script, i checked logs and UI, so the order was created successfully as shown below from logs: create the installation order: Payload: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:createWorkOrder xmlns:ns3="http://server.api.nep.mobinets.com/"> <woNo>I1421287958</woNo> <arborOrderId>268710598</arborOrderId> <orderTypeName>20</orderTypeName> <subscriberNo>23279442</subscriberNo> <appType>SWITCHING</appType> <woOperation>Shifting Installation</woOperation> <equipementId/> <autoCreateTasks>false</autoCreateTasks> <login>96441</login> <exchange1>XR97</exchange1> <oldSubscriberNo>23234094</oldSubscriberNo> </ns3:createWorkOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> create the termination order: Payload: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:createWorkOrder xmlns:ns3="http://server.api.nep.mobinets.com/"> <woNo>T1421287958</woNo> <arborOrderId>268710598</arborOrderId> <orderTypeName>21</orderTypeName> <subscriberNo>23234094</subscriberNo> <appType>SWITCHING</appType> <woOperation>Shifting Termination</woOperation> <equipementId/> <autoCreateTasks>false</autoCreateTasks> <login>96441</login> <exchange1>XR97</exchange1> </ns3:createWorkOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
        Hide
        added a comment -

        Please ignore my last email since the query was wrong,
        The only record from 08 January till now is the below:

        ID wo_no method_name error code error message time_out Start Date end date sub_no arbor order id
        -2921695 1421287958 arborMoveExt_fCNAMOVE 0 30000 24-Feb-25 24-Feb-25 23279442 268710598

        Show
        added a comment - Please ignore my last email since the query was wrong, The only record from 08 January till now is the below: ID wo_no method_name error code error message time_out Start Date end date sub_no arbor order id -2921695 1421287958 arborMoveExt_fCNAMOVE 0 30000 24-Feb-25 24-Feb-25 23279442 268710598
        Hide
        Abir Messaikeh added a comment -

        under monitoring , we need to detect a new case to fix permanently

        Show
        Abir Messaikeh added a comment - under monitoring , we need to detect a new case to fix permanently
        Hide
        Sara Saddik added a comment - - edited

        To check from DB for new cases if they occur:

        SELECT *
        FROM FN_PROCESS_ORDER fpo
        WHERE fpo.ERROR_CODE = '0'
        AND fpo.start_date > TO_DATE('08-JAN-2025', 'DD-MON-YYYY')
        AND NOT EXISTS (
        SELECT 1
        FROM FN_WORK_ORDER fwo
        WHERE fwo.WO_NO LIKE '%' || fpo.WO_NO || '%'
        );

        Show
        Sara Saddik added a comment - - edited To check from DB for new cases if they occur: SELECT * FROM FN_PROCESS_ORDER fpo WHERE fpo.ERROR_CODE = '0' AND fpo.start_date > TO_DATE('08-JAN-2025', 'DD-MON-YYYY') AND NOT EXISTS ( SELECT 1 FROM FN_WORK_ORDER fwo WHERE fwo.WO_NO LIKE '%' || fpo.WO_NO || '%' );
        Hide
        Sara Saddik added a comment -

        Logs have been added to the implementation to be reviewed later when the same case occurs

        Show
        Sara Saddik added a comment - Logs have been added to the implementation to be reviewed later when the same case occurs

          People

          • Assignee:
            Salem Dannawi
            Reporter:
            Salem Dannawi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 days, 3 hours, 30 minutes
              2d 3h 30m

                Drag and Drop