Kbase P4959: Broker does not start when batch/script file attempts to sta
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/16/2003 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 2.x
FACT(s) (Environment):
WebSpeed 3.x
SYMPTOM(s):
Broker does not start
Batch or Script file is used to start and stop broker
Batch or Script file is implemented through Windows scheduler
Through a batch/script process, the database is shutdown before the WS broker is shutdown
Through a batch/script process, the WS broker is started before the database is started.
WS broker connects to database at startup with -H, -S, -N
CAUSE:
The root cause of this issue is the order of events that occur in the batch/script process. Here the WS broker tries to connect to the database before the database is up and running.
FIX:
Order the events within the batch/script file to:
1. Stop the WS broker before the database shutdown
2. Start the database
3. Start the WS broker after the database has successfully started