1. David Vasconcelos
  2. PowerServer 2020 or older (Obsolete)
  3. Tuesday, 18 June 2019 10:54 AM UTC

We are experiencing timeout issues.  When the DBA does a restore of a database which is on the same server as the one we are using we have noticed during that process datawindows/sql have been timing out.  When a restore occurs the process does consume 80% of the CPU on the box.  Is there a setting that needs to be adjusted.  On AEM we do have our transaction time out set for 120 seconds but we are experiencing these time outs around 30 seconds or so.

PB 2017 r3, Powerserver 2017, Sybase ASE 16.

Dave V.

David Vasconcelos Accepted Answer Pending Moderation
  1. Tuesday, 18 June 2019 14:09 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Found the issue, Sybase Command time out by default is set to zero but in AEM the datasource default was set to 30 seconds.  Once we changed that it took care of the problem Note we changed it to be zero. 

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.