Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Progress 9.1C

FACT(s) (Environment):

Windows 2000

SYMPTOM(s):

Abnormal communication failure for config: (8490)

In crash handler for config . (8486)

The Database and system was running slowly before crashing

Databases managed by the AdminServer.

Some Databases managed by the AdminServer will not register at AdminServer startup

CAUSE:

Could be related to bug 20011009-008 (patched in 9.1C12) or 20000714-021
Possible cause the problem with the AdminServer not waiting enough for the DB start.

FIX:

Suggested Workaround:

- increase RTInitializing from 4 (seconds) to 30 seconds;
this is the # of seconds the AdminServer waits to get an initialization acknowledgement from _mprosrv.

- increase RTStarting from 4 (seconds) to 30 seconds;
this is the # of seconds the AdminServer wait to get a starting acknowledgement from _mprosrv.

- increase RTShuttingDown from 0 (seconds) to 30 seconds


note: If any of the acknowledgements are received prior to the timeout period, no further waiting is done.
If no acknowledgement is received prior the timeout, the AdminServer stops trying to communicate with the _mprosrv process and the user will see the "time out" message in the database log file.


Increase the timeout:
----------------------

1. You need to stop the AdminServer

2. Add the above recommendations to a file, say "newTimings" for example, in
the form:
RTInitializing=30
RTStarting=30
RTShuttingDown=30

3. Add the java property, -DConfigToolTimings=<dirPath>
ewTimings, to the
AdminServer startup command.
This can be done by modifying the "proadsv" file to include this java property or by adding the property to the "JVMARGS" environment variable.

4. Start the AdminServer.