Details

    • Customer:
      OMAN-Tel

      Description

      Please note that NON IP xml import failed due to below error during the saving to DB.

      Please find the server logs during the import and xml in following link.
      https://mobinets-my.sharepoint.com/personal/mohan_rathor_mobinets_com/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fmohan%5Frathor%5Fmobinets%5Fcom%2FDocuments%2FhuaweiIPxml%2Fserver%2Erar&parent=%2Fpersonal%2Fmohan%5Frathor%5Fmobinets%5Fcom%2FDocuments%2FhuaweiIPxml&ga=1

      https://mobinets-my.sharepoint.com/personal/mohan_rathor_mobinets_com/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fmohan%5Frathor%5Fmobinets%5Fcom%2FDocuments%2FhuaweiIPxml%2F2025%2D08%2D29%2D10%2E15%2E32%5FNONIP%5FOmanTel%2Exml%2Etar%2Egz&parent=%2Fpersonal%2Fmohan%5Frathor%5Fmobinets%5Fcom%2FDocuments%2FhuaweiIPxml&ga=1

      Start Import :- 2025-08-31 08:36:26

      Caused by: Error : 1400, Position : 148, Sql = insert into nep_prod.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into nep_prod.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-01400: cannot insert NULL into ("NEP_PROD"."LTECELL"."ENODEBID")
      Failed SaveOrUpdate com.mobinets.nps.model.network.fourg.LteCell.: org.hibernate.exception.ConstraintViolationException: could not execute statement
      Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("NEP_PROD"."LTECELL"."ENODEBID")

      2025-08-31 10:52:01,062 ERROR [com.mobinets.nps.services.imtDataInput.impl.ImtCreateWS] (Thread-127) Unavailable Service 'Save to Database'.: org.hibernate.exception.Co
      nstraintViolationException: could not execute statement
      2025-08-31 10:52:01,067 INFO [stdout] (AsyncAppender-Dispatcher-Thread-99) 10:52:01-[FATAL][SaveRunner] Error while calling saving instances to Database: [User: importer][Action: com.mobinets.nep.npt.service.AutoImportService.importNetwork(String, String, NEPBundles, ImporterParams) 0b5c9c14-178c-45df-beb6-b7097f455b3e]
      2025-08-31 10:51:45,751 ERROR [com.mobinets.nps.bo.imtDataInput.impl.NetworkCreateManager] (Thread-127) error while flushing and clearing session saveToDatabase...: org.hibernate.exception.ConstraintViolationException: could not execute batch

      Yesterday again we ran Huawei IP xml so still we are getting DEADLOCK APPARENT error.

      2025-08-28 10:15:14,229 INFO [stdout] (C3P0PooledConnectionPoolManager[identityToken->2yb85obc1tunfk216u02tt|2a46c3a5]-AdminTaskTimer) 33280937 [C3P0PooledConnectionPoolManager[identityToken->2yb85obc1tunfk216u02tt|2a46c3a5]-AdminTaskTimer] WARN com.mchange.v2.async.ThreadPoolAsynchronousRunner - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1b589fcd – APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
      2025-08-28 10:15:14,229 INFO [stdout] (AsyncAppender-Dispatcher-Thread-99) 10:15:14-[WARN ][ThreadPoolAsynchronousRunner] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@3a07aa21 – APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

      Here are the details for the recent XML import attempts:
      1. HUAWEI IP XML Import
      • File: 2025-08-28-02.52.47_OmanTel.xml
      2025-08-28-02.52.47_OmanTel.xml.tar.gz
      • Import Start Time: 2025-08-28 03:09:46
      • Maximum Resource Utilization:
      o Memory: 325.4 GB
      o AI Memory: 7.7 GB
      o CPU: 3512%
      Note: The JBoss process is allocated 340 GB of memory and the system has a 48-core CPU."
      XML import process excel and logs are attached in attachment.

        Activity

        Hide
        Marwan Kanaan added a comment -

        Dear Team,
        Kindly note that I will modify the constraint on LTECELL.ENODEBID to allow NULL values temporarily. After this change, please restart the PROD server and reimport the full NON-IP XML. This will help us identify the LTECELL records with ENODEBID set to NULL, so we can generate a smaller XML for testing and work toward a permanent solution.
        Thank you for your support.
        Best Regards,

        Marwan Kanaan I Software Developer

        Show
        Marwan Kanaan added a comment - Dear Team, Kindly note that I will modify the constraint on LTECELL.ENODEBID to allow NULL values temporarily. After this change, please restart the PROD server and reimport the full NON-IP XML. This will help us identify the LTECELL records with ENODEBID set to NULL, so we can generate a smaller XML for testing and work toward a permanent solution. Thank you for your support. Best Regards, Marwan Kanaan I Software Developer
        Hide
        Marwan Kanaan added a comment -

        Dear @Mohan Singh Rathor,

        Please be aware that this exception has been successfully resolved.

        Apply patch 3.0.7.1346 and verify.

        Best Regards,
        Marwan

        Show
        Marwan Kanaan added a comment - Dear @Mohan Singh Rathor, Please be aware that this exception has been successfully resolved. Apply patch 3.0.7.1346 and verify. Best Regards, Marwan
        Hide
        Marwan Kanaan added a comment -

        Dear Team,

        Kindly note that I have rechanged the LTECELL.ENODEBID to NOT NULL. After investigating and working on the LTE Cell, I have provided a permanent solution for the cases where the EnodeB ID was null.
        However, the deadlock issue still requires further work to be resolved.
        Please restart the PROD server and apply the patch that includes the LTE solution.
        Patch NB: 3.7.0.1347.

        Best Regards,

        Marwan Kanaan I Software Developer

        Show
        Marwan Kanaan added a comment - Dear Team, Kindly note that I have rechanged the LTECELL.ENODEBID to NOT NULL. After investigating and working on the LTE Cell, I have provided a permanent solution for the cases where the EnodeB ID was null. However, the deadlock issue still requires further work to be resolved. Please restart the PROD server and apply the patch that includes the LTE solution. Patch NB: 3.7.0.1347. Best Regards, Marwan Kanaan I Software Developer

          People

          • Assignee:
            Abir Messaikeh
            Reporter:
            Salem Dannawi
          • Votes:
            0 Vote for this issue
            Watchers:
            2 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 - 1 day, 1 hour
              1d 1h

                Drag and Drop