Mobinets-JIRA

Mobinets-JIRA http://jira.mobinets.com/jira This file is an XML representation of an issue en-us

6.1.4

6159

19-11-2013

[LS-382] FN long running DB Session http://jira.mobinets.com/jira/browse/LS-382 L3 Support <p>FN long running DB Session</p> LS-382

FN long running DB Session

Bug Normal Cancelled Cannot Reproduce Khaled Khalil Salem Dannawi Wed, 14 May 2025 10:22:09 +0300 Wed, 15 Apr 2026 11:02:08 +0300 Wed, 15 Apr 2026 11:02:08 +0300 FN Fri, 16 May 2025 00:00:00 +0300 0 2 <p>Dear Abir</p> <p>Please note that there is no historical table available to check the frequency of long-running sessions. However, such occurrences have been no frequent and have only happened 3 or 4 times this year.</p> <p>Best,</p> <p>From: Abir Messaikeh <Abir.Messaikeh@nuiva.com> <br/> Sent: Tuesday, May 13, 2025 11:57 AM<br/> To: Natnael Asfaw <Natnael.Asfaw@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com><br/> Cc: Malek Ibrahim <Malek.Ibrahim@mobinets.com>; support <support@mobinets.com>; integration <integration@mobinets.com>; Hassan Abdine <Hassan.Abdine@nuiva.com><br/> Subject: RE: FN functions not working due to DB lock </p> <p>Dear Natnael </p> <p>Could u please check in last 1 year , how frequent this long running session happened impacting FN activity and was it for same query if we have such information </p> <p>As Integration feedback was that nothing abnormal was observed on DB , I will raise it to L3 to see if this is something that needs to be adjusted but such information about occurrence frequency is useful</p> <p>Thx<br/> Abir</p> <p>From: Natnael Asfaw <Natnael.Asfaw@mobinets.com> <br/> Sent: Thursday, May 8, 2025 4:56 PM<br/> To: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; support <support@mobinets.com>; integration <integration@mobinets.com><br/> Cc: Malek Ibrahim <Malek.Ibrahim@mobinets.com><br/> Subject: RE: FN functions not working due to DB lock </p> <p>Dear Abir</p> <p>Please find attached the long-running SQL sessions that were active during the NEP issue and may have caused to the database deadlock</p> <p>Best,</p> <p>From: Abir Messaikeh <abir.messaikeh@nuiva.com> <br/> Sent: Thursday, May 8, 2025 3:09 PM<br/> To: Yasssin Geehad <Yasssin.Geehad@omantel.om>; support <support@mobinets.com>; integration <integration@mobinets.com><br/> Cc: NGOSS_Support <NGOSS_Support@omantel.om>; Hamed Hamid Saif Al Sulaimani <hamed.sulaimani@omantel.om><br/> Subject: RE: FN functions not working due to DB lock </p> <p>++ Integration to check promptly</p> <p>Regards<br/> From: Yasssin Geehad <Yasssin.Geehad@omantel.om> <br/> Sent: Thursday, May 8, 2025 3:05 PM<br/> To: Abir Messaikeh <abir.messaikeh@nuiva.com>; support <support@mobinets.com><br/> Cc: NGOSS_Support <NGOSS_Support@omantel.om>; Hamed Hamid Saif Al Sulaimani <hamed.sulaimani@omantel.om><br/> Subject: FN functions not working due to DB lock </p> <p>Dear @Abir Messaikeh , </p> <p>Please support as FN main functionalities not working. </p> <p>2025-05-08 16:02:43.808 <span class="error">[https-jsse-nio-8450-exec-24]</span> INFO c.m.n.c.workflow.soap.SoapDelegate - >>> End Executing Service With Exception: "I/O error: Connection reset; nested exception is java.net.SocketException: Connection reset" SoapDelegate.FnService.updateOltPort</p> <p>2025-05-08 16:02:43.809 <span class="error">[https-jsse-nio-8450-exec-24]</span> ERROR c.m.n.c.workflow.soap.SoapDelegate - I/O error: Connection reset; nested exception is java.net.SocketException: Connection reset<br/> org.springframework.ws.client.WebServiceIOException: I/O error: Connection reset; nested exception is java.net.SocketException: Connection reset<br/> 2025-05-08 16:02:43.809 <span class="error">[https-jsse-nio-8450-exec-24]</span> INFO c.m.n.c.workflow.soap.SoapDelegate - >>> End Executing Service: FnService|updateOltPort|300934.0|ms|KO|WebServiceIOException|I/O error: Connection reset; nested exception is java.net.SocketException: Connection reset<br/> <span class="error">[nep@wat-sf-nep-ws01p-v:6 logs]</span>$ utmpdump</p> <p>Regards,<br/> Yasssin</p> <p>to confirm by hassan if we need to close this ticket</p> <p>no new occurence for now , closing it and will re-open if happens again</p> Customer Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Fri, 16 May 2025 00:00:00 +0300 Planned Start Fri, 16 May 2025 00:00:00 +0300 Rank 0|xtimjl: Rank (Obsolete) 9223372036854775807 VTDirections