Kbase P98452: What do the AdminServer timing values mean in the admserv.log file?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/08/2007 |
|
Status: Unverified
GOAL:
What do the adminserver timing values mean in the admserv.log file?
GOAL:
How to adjust the amount of time AdminServer will wait for a database to startup.
GOAL:
What do the (8465) messages mean?
FACT(s) (Environment):
Progress 9.1C
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
FIX:
Below are the names of the timing variables, their defined defaults, and a description of what the timing variables control.
Timing values: (8464)
rtinitializing=4 (8465)
The number of seconds the AdminServer waits to get an initialization acknowledgement from _mprosrv.
auxstartupdelay=2 (8465)
wtcstarting=120 (8465)
Individual databases will wait either the number of seconds displayed in WTCStartingMin or ( WTCStarting * numberOfAutostarts) whichever is the greater when multiple database are set to autostart.
sgstartupdelay=2 (8465)
The number of seconds the database plugin will wait after the primary broker is started to start the secondary broker.
wtcinitializing=120 (8465)
Individual databases will wait either the number of seconds displayed in WTCInitialingMin or ( WTCInitialing *numberOfAutostarts ) whichever is the greater when multiple database are set to autostart.
pollservergroup=11 (8465)
This timer dictates the poll interval in seconds that the auxiliary and secondary broker processes will be polled to determine when they are running. Polling ends when the processes are either running or have failed to start. Processes such as after image processes, before image processes, watch dogs, and after page writers, are examples of auxiliary processes.
wtcinitializingmin=300 (8465)
At minimum, the database object will wait up to WTCInitializingMin seconds for a successful state transition. Once a database object has established communication between itself and its _mprosrv process, validation occurs before the database object can transition from the starting state -> initializing state. These timers control how long this validation process can take. Timers are terminated immediately upon successful state transition, or in worse case, when the timer expires. If the timer expires, the database object is forced back to the idle state.
continitializing=4 (8465)
Messages sent by the database broker to the database plugin to continue waiting an additional x number of seconds for the initialized messages.
dbstartupdelay=5 (8465)
If any registrations have occurred, then the database plugin polls every DbStartupDelay seconds until no more registrations are received between polls.
wtcshuttingdown=120 (8465)
If multiple databases are being autostarted at database plugin startup, the time required to make the state transition can be longer. As a result, the individual databases will wait WTCShuttingDown*numberOfAutostarts or WTCShuttingDownMin seconds, which ever is greater.
contshuttingdown=4 (8465)
Messages sent by the database broker to the database plugin to "continue" waiting an additional X number of seconds for the shutting messages.
contstarting=2 (8465)
Messages sent by the database broker to the database plugin to "continue" waiting an additional X number of seconds for the starting messages.
wtcshuttingdownmin=300 (8465)
At minimum, the database object will wait up to WTCShuttingDownMin seconds for a successful state transition. Before a database is shut down, it is in the running state. During database shut down, databases transition from the running state -> shutting down state -> idle state. These timers control how long the shutdown process can take before the database is assumed crashed. Timers are terminated immediately upon successful state transitio.n, or in worse case, when the timer expires. If the timer expires, the database is assumed crashed and the database object is forced back to the idle state.
rtstarting=2 (8465)
The number of seconds the AdminServer wait to get a starting acknowledgement from _mprosrv.
wtcstartingmin=300 (8465)
At minimum, the database will wait up to WTCStartingMin seconds for a successful state transition.
dbstartupdelaymin=10 (8465)
These parameters control how long the database plugin will wait before checking if any more registrations between database objects and their _mprosrv processes have occurred. At a minimum, the database plugin will wait the number of DbStartupDelayMin seconds for any registrations to occur. If no registrations have occurred, no more waits for subsequent registrations are done.
There is also a way to disable timeouts for the AdminServer for any and all databases it would start with DBMan.
To disable all timeout values for databases, JVMARGS should include "-DBypassDatabaseTimings=true" on the AdminServer startup line.
This was added to 9.1E and 10.0B
.