Question

7
Replies
148
Views
Close popover
Anand Pandey (AnandP)
Swedbank AB
Pega Platform Engineer
Swedbank AB
SE
AnandP Member since 2013 142 posts
Swedbank AB
Posted: August 31, 2020
Last activity: September 14, 2020

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." ? 

Pega Platform 8.4.2 Case Management Financial Services Senior System Architect