Recently we have faced issue in our SAP Process Orchestration system where all DB connections were getting occupied after starting in few minutes.
We have identified the cause of this issue where 1 of our channel is sending thousands of messages to third party & due to delay in acknowledgment, it’s consumed all the DB process & system get hung.
We found that after even restart of application servers, DB connections were not getting destroyed automatically even though there enough DB connections are free at DB side. The issue is lying under application layer & below error is occurring Default Trace –
Exception of type com.sap.sql.log.OpenSQLException caught: No connection to data source SAP
Default DB Pool size = 100
There is an standard SAP note where SAP is suggesting to increase the value from 100 to 250 of respective parameter in Config Tool & restart the system. we tried the same but after restart 250 connections completely occupied & same issue was occurring.
PO team identified the channel & stop the channel temporarily to avoid the issue & system back to Normal. They have cleared the stuck message & restart the channel after some time.
Now from BASIS side our responsibility is to Monitor the DB connections to avoid the hanging situation. we found below URL to monitor the DB connections & also destroy the same if requires.
http:// hostname:port number/OpenSQLMonitors
The above URL is just like ST04 of any ABAP system & it’s very useful to monitor your critical SAP JAVA system regularly to avoid any unscheduled downtime.