Kbase P6277: Use 3.1D DATABASES environment variable to avoid errors 2659 and 9545
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 3.1D
SYMPTOM(s):
Disconnect from server; database is being shutdown. (2659)
Disconnecting from database <database>, user number <usernum>. (9545)
Errors 2659 and 9545 are present within the webspeed server log
Browser returns: Page can not be found
Database is always active when error occurs
Database was shut down for backup while 1 webspeed agent is connected at AVAILABLE
While database backup occurs, webspeed broker can not be shutdown
CAUSE:
If 1 agent is connected to database and database is shutdown & brought back up, the agents does not have an automatic database-reconnection mechanism. If the agent is not doing any processing, it sits in a WAIT-FOR loop waiting for a WEB-NOTIFY event (as coded in web-disp.p). Once it receives this event, and tries to process something against the database, it will then realize that the database has been disconnected, thus the reason why error 2659 and 9545 are written to the log file. This is standard and expected behavior.
FIX:
Use 3.1D webspeed new environment variable DATABASES to check if the database is connected, and connect to the database if it is not connected. For details, reference Progress solution:
P22658, What is the new DATABASES environment variable in webspeed 3.1D?