L3 Support
  1. L3 Support
  2. LS-492

com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls.

    Details

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

      Description

      NEP is rejecting below order with an error:: com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls.
      Please support to trouble shoot this error.

      Note::As shown below getting this error while calling FN service internally.

      <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:arborSingleWO_fCNA xmlns:NS3="http://server.api.nep.mobinets.com/">
      <fAppType>I</fAppType>
      <fExc>XA54</fExc>
      <fCabinet>054M</fCabinet>
      <fDpoint>0001</fDpoint>
      <fSubno>25884397</fSubno>
      <fSubscr_Type>T</fSubscr_Type>
      <fWOID>1508942054</fWOID>
      <fUsage_Type>2</fUsage_Type>
      <fOrder_Type>INST</fOrder_Type>
      <fUserID>95394</fUserID>
      <arborOrderId>277828781</arborOrderId>
      </NS3:arborSingleWO_fCNA>
      </NS1:Body>
      </NS1:Envelope>

      2025-07-07 10:59:24.082 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.AuditServiceAdvice - >>> Start calling > arborSingleWO_fCNA
      2025-07-07 10:59:24.082 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - Start --> build Order Request
      2025-07-07 10:59:24.082 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - End --> build Order Request
      2025-07-07 10:59:24.082 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - Start --> fetching Old Record.
      2025-07-07 10:59:24.888 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - End --> fetching Old Record.
      2025-07-07 10:59:24.888 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - Getting Old Order with: woNo1508942054 errorCode: 63 methodName: arborSingleWO_fCNA
      2025-07-07 10:59:24.888 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - Start --> saving request iteration1
      2025-07-07 10:59:24.902 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - End --> saving request iteration1
      2025-07-07 10:59:24.902 [https-jsse-nio-8451-exec-85] INFO c.m.n.api.server.OrderRequestAdvice - Start --> invocation.proceed
      2025-07-07 10:59:24.902 [https-jsse-nio-8451-exec-85] INFO c.mobinets.toolbox.app.EventProducer - Event was added to the queue: [95394], [ARBORSINGLEWO_FCNA_API_ACTION]
      2025-07-07 10:59:24.902 [Thread-4] INFO c.m.t.a.EventProducer$EventConsumer - ...consuming event [95394], [ARBORSINGLEWO_FCNA_API_ACTION]
      2025-07-07
      2025-07-07 10:59:25.112 [Thread-4] INFO c.m.t.a.EventProducer$EventConsumer - ...consuming event [NEP], [CHECKNEWACTIVATIONCOPPERFEASIBILITY_API_ACTION]
      2025-07-07 10:59:25.267 [https-jsse-nio-8451-exec-22] ERROR c.m.nep.api.server.FnServiceImpl - com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls
      com.mobinets.nep.npt.service.model.NptException: com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP-ENV:Header />
      <SOAP-ENV:Body>
      <ns3:checkNewActivationCopperFeasibility xmlns:ns3="http://server.api.nep.mobinets.com/">
      <exchange>XA54</exchange>
      <cab>054M</cab>
      <dp>0001</dp>
      <serviceTypeName>PSTN+ADSL</serviceTypeName>
      </ns3:checkNewActivationCopperFeasibility>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <ns2:checkNewActivationCopperFeasibilityResponse
      xmlns:ns2="http://server.api.nep.mobinets.com/">
      <return>
      <responseCode>1</responseCode>
      <responseMessage>com.querydsl.core.NonUniqueResultException: Only one result is
      allowed for fetchOne calls</responseMessage>
      </return>
      </ns2:checkNewActivationCopperFeasibilityResponse>
      </soap:Body>
      </soap:Envelope>

        Activity

        Show
        Salem Dannawi added a comment - https://mobinets-my.sharepoint.com/personal/mohan_rathor_mobinets_com/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fmohan%5Frathor%5Fmobinets%5Fcom%2FDocuments%2FhuaweiIPxml%2FRR%2D07%2D07%2D2025%2D14%2D41&ga=1
        Hide
        Abir Messaikeh added a comment -

        2 nodes with same Object ID available

        Show
        Abir Messaikeh added a comment - 2 nodes with same Object ID available
        Hide
        Abir Messaikeh added a comment -

        There is no code issue related to this ticket.
        The code is designed to retrieve a node (MDF, ODF, ...), and each node in NEP should have a unique ID composed of the version ID and the object ID.
        In that scenario, when you attempted to create an order, one of the nodes being used was created twice in the database with the same object ID and the same version ID, which is incorrect. NEP should not allow duplicate entries with the same IDs (you may want to investigate this later).
        Therefore, this is a data issue. Please identify the duplicated node and delete one of the them.

        Show
        Abir Messaikeh added a comment - There is no code issue related to this ticket. The code is designed to retrieve a node (MDF, ODF, ...), and each node in NEP should have a unique ID composed of the version ID and the object ID. In that scenario, when you attempted to create an order, one of the nodes being used was created twice in the database with the same object ID and the same version ID, which is incorrect. NEP should not allow duplicate entries with the same IDs (you may want to investigate this later). Therefore, this is a data issue. Please identify the duplicated node and delete one of the them.

          People

          • Assignee:
            Salem Dannawi
            Reporter:
            Salem Dannawi
            Rejected By:
            Abir Messaikeh
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

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

              Drag and Drop