Question5Replies395Views×Close popoverJohn Lordo (JohnL881) Infosys Infosys US View Profile JohnL881 Member since 2013 15 posts Infosys Posted: March 22, 2017Last activity: April 3, 2017Posted: 22 Mar 2017 12:28 EDTLast activity: 3 Apr 2017 9:37 EDT Closed Solved PEGA0026 Alert message parametersHello everybody,while troubleshooting performance issued I stumbled over many Pega0026 alerts and this descriptive article: https://pdn.pega.com/pega0026-alert-time-connect-database-exceeds-limit/pega0026-alert-time-connect-database-exceedsIt mentions the structure of these messages:Time to acquire a connection has exceeded the alert threshold of 100 ms: 152 ms. DBName [pegarules] Initial [False] Connection  Status [New] Type [JDBC URL Common] Conn Mgr [Pega]Some of the parameters are self explanatory, such as "DBName". I couldn't find an explanation for all of the others:InitialConnectionStatusTypeConn MgrThe log files suggests the message is created in the 'com.pega.pegarules.data.internal.access.ConnectionManagerImpl' class.Is there some documentation available what these parameters are? System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoPosted: 23 Mar 2017 5:35 EDT×Close popoverAkshay Kumar Sinha (AkshaySinha) PEGA Senior Technical Solutions Engineer Pegasystems Inc. IN View ProfileAkshaySinha PEGA replied to JohnL881Hello, Please have a look on the below article: https://pdn.pega.com/troubleshooting-pega0026-alerts-indicate-connection-pool-settings-too-low Thanks. Posted: 3 years agoPosted: 23 Mar 2017 8:41 EDT×Close popoverJohn Lordo (JohnL881) Infosys Infosys US View ProfileJohnL881 Infosys replied to AkshaySinhaThank you, Akshya. I was aware of that article. My question is not how to troubleshoot but rather to better understand the alert message. An explanation of those parameters would help a lot. Accepted Solution Posted: 3 years agoPosted: 23 Mar 2017 9:15 EDT×Close popoverUmamaheshwar Reddy Midthuru (Mahesh Midthuru) PEGA Sr. Software Solutions Engineer Pegasystems Inc. US View ProfileMahesh Midthuru PEGA replied to JohnL881Hi John, I couldn't find the documentation regarding this class, but after looking into the code got an idea of what these parameters are explained as follows: Initial - it says whether the connection is made first time or not i.e. True/False Connection - contains the unique connection id value or null value Status - this field specifies the status of the connection that can be New/Existing/Reserved Type - this field contains the information of JDBC URL/JNDI Name Conn Mgr - this field specifies which type of connection mechanism is being followed i.e it can be App Server/Pega Hope this information might be helpful to you. Regards Mahesh Posted: 3 years agoPosted: 3 Apr 2017 9:37 EDT×Close popoverJohn Lordo (JohnL881) Infosys Infosys US View ProfileJohnL881 Infosys replied to Mahesh MidthuruHello Mahesh, thank you for the helpful reply. If possible, can you elaborate on the difference between 'Initial' and 'Status'? In my understanding an 'Initial' value of 'true' will always lead to a 'Status' of 'New' and a an 'Initial' value of false would lead to a 'Status' of 'Existing'. Is that correct? Posted: 3 years agoPosted: 24 Mar 2017 10:23 EDT×Close popoverSatish Tripathi (PERKSATISH) JP Morgan Chase JP Morgan Chase US View ProfilePERKSATISH JP Morgan Chase replied to JohnL881For Pega0026 alerts please see your connection pool size. Increasing the connection pool size should fix the issue unless there are some process that are eating up resources. Check for Pega0005 alerts in your log before increasing the pool size.