Details
-
Type:
Bug
-
Status:
Cancelled
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Labels:None Labels
-
Customer:Zain Kuwait
Description
As checked and found NEP get download while saving to DB, getting below error message. So request you to please align resource to rectify this and Jira ticket will raise once Jira work.
Download log from below link.
server.log.kw.15.03.2026.tgz
2026-03-15 02:26:36,640 ERROR [com.mobinets.nps.bo.imtDataInput.impl.NetworkCreateManager] (Thread-125) error while flushing and clearing session saveToDatabase...: org.hibernate.exception.ConstraintViolationException: could not execute batch
2026-03-15 02:26:37,079 ERROR [com.mobinets.nps.services.imtDataInput.impl.ImtCreateWS] (Thread-125) Unavailable Service 'Save to Database'.: org.hibernate.exception.ConstraintViolationException: could not execute batch
2026-03-15 02:26:37,080 INFO [stdout] (AsyncAppender-Dispatcher-Thread-108) 02:26:37-[FATAL][SaveRunner][Thread-125] Error while it will may calling saving instances database
2026-03-15 02:26:37,080 FATAL [com.mobinets.nep.npt.db.ThreadSaveContainer] (Thread-125) Error while saving: java.lang.RuntimeException: com.mobinets.nep.npt.service.model.NptException: com.mobinets.nps.model.exception.NpsException: org.hibernate.exception.ConstraintViolationException: could not execute batch
at com.mobinets.nep.npt.db.SaveRunner.run(SaveRunner.java:82)
at com.mobinets.nep.npt.db.ThreadSaveContainer$1.run(ThreadSaveContainer.java:77)
Caused by: com.mobinets.nep.npt.service.model.NptException: com.mobinets.nps.model.exception.NpsException: org.hibernate.exception.ConstraintViolationException: could not execute batch
... 2 more
Caused by: com.mobinets.nps.model.exception.NpsException: org.hibernate.exception.ConstraintViolationException: could not execute batch
at com.mobinets.nps.services.imtDataInput.impl.ImtCreateWS.saveToDatabase(ImtCreateWS.java:93)
at com.mobinets.nep.npt.db.SaveRunner.run(SaveRunner.java:70)
... 1 more
Caused by: org.hibernate.exception.ConstraintViolationException: could not execute batch
2026-03-15 02:26:37,133 WARN [org.springframework.remoting.rmi.RmiServiceExporter] (Thread-125) RMI service 'FloorPlanService' is not bound to registry at port '10246' anymore: java.rmi.NotBoundException: FloorPlanService
2026-03-15 02:26:42,112 ERROR [stderr] (Thread-125) Caused by: javax.management.JMException: Agent already registred with the same domain:NEPAgent
2026-03-15 02:26:42,112 ERROR [stderr] (Thread-125) at com.mobinets.nep.management.connectors.LocalVM.registreNepAgent(LocalVM.java:361)
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 1 hour
-
Update Customer about the RCA provided by L3
-
- Time Spent:
- 1 hour
-
Joined the teams meeting with Cybermak team for discuss on going task.
-
- Time Spent:
- 1 hour
-
Next day analyze the log about running task and shared output to L3.
-
- Time Spent:
- 6 hours
-
Testing (Run the passive IT and XML ) and validate the same
-
- Time Spent:
- 3 hours, 30 minutes
-
Run the passive IT manual on test platform then copied dump from prod to test then generate XML manual.
After new hours got confirmation from L1 to re-run passive IT manual so run again and analyze the log.
-
- Time Spent:
- 3 hours
-
Testing the latest patch to reproduce the issue
-
- Time Spent:
- 1 hour, 30 minutes
-
Patch has been applied on kuwait test platform.
-
- Time Spent:
- 1 hour
-
Issue rasied with Ticket created
-
- Time Spent:
- 3 hours, 30 minutes
-
Checked the application status in morning along with analyze the log after rollback AI patch and looks fine, as per request log and XML shared with L3 team and patch applied on test platform which released.
-
- Time Spent:
- 3 hours
-
Analyze the log and check the application and found down then restart them, during log check found application get down while saving to db therefor raised to L3 to fix it and as per confirmation rollback AI patch.
-
- Time Spent:
- 2 hours, 30 minutes
-
Analyze the log and check the application status and found down therefor restart all the application.
