Question
Nordea
SE
Last activity: 14 Sep 2020 11:02 EDT
Socket Timeout Exception - StaleConnectionException
Hi,
We get below error frequently in all our test & production environments:--
here was a problem with the database when getting a list: com.pega.pegarules.pub.database.ConnectionException: Database-General Connection Exception 17002 08006 IO Error: Socket connect timed out DSRA0010E: SQL State = 08006, Error Code = 17,002 DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.StaleConnectionException: IO Error: Socket connect timed out DSRA0010E: SQL State = 08006, Error Code = 17,002 | SQL Code: 17002 | SQL State: 08006
DatabaseException caused by prior exception: java.sql.SQLRecoverableException: IO Error: Socket connect timed out DSRA0010E: SQL State = 08006, Error Code = 17,002 | SQL Code: 17002 | SQL State: 08006
I understand socket timeout can due to many reasons, application code, networking, service implementation but could you suggest where we shall look first?
As per the suggestion given in the article - https://www.ibm.com/support/pages/websphere-application-server-staleconnectionexception, Is it possible to implement this recommendation: "Write your application code to catch SCE's and retry the connection request x number of retries. This is the preferred method." ?
Pegasystems Inc.
US
what is your WAS datasource configuration? Can you show some screenshots? What is your connection pool purge policy (should be Entire Pool).
Updated: 1 Sep 2020 6:14 EDT
Nordea
SE
Hi @KevinZheng_GCS , here in the screenshot you can find the connection pool setting for each data source (we are using dual user setup). We were using Entire Pool earlier but that didn't help. now we are using other settings (FailingConnectionOnly) to check if it can help but no improvement
Ford Motor Company
US
Purge Policy, I prefer to choose "FailingConnectionOnly" instaed of EntirePool.
In order to better understand the Connection details, you can review by enabling the monitoring and analyze how your connections are being used at Peak usage,
IBM WebSphere Admin Console > Monitoring and Tuning > Performance Viewer > Current activity > Select a JVM and Click Start Monitoring > Click the JVM Selected above > Expand the JVM > Performance Modules > Select JDBC Connection Pools > Hit 'View Module(s) Button > Leave it for some time > Stop Logging > Observe the Usage Details.
Based on the USage you can adjust couple Connection Pool Settings, attached screenshots of my environment.
compare and adjust the connection pool from the screenshot
Statement Cache --> 75 for Non PROD, 100 for PROD [Depending on the Usage ]
Also, check with your DataBase Administrator for any Connection Waits at the Database.