Kbase P130558: How to troubleshoot error 8619 for databases started with AdminServer or Progress Explorer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
How to troubleshoot error 8619 for databases started with AdminServer or Progress Explorer
GOAL:
How to get more information about database startup failure
GOAL:
How to find detailed errors for databases started via AdminServer
GOAL:
How to get more details about the database startup with AdminServer
GOAL:
** This process terminated with exit code <number>. (8619)
GOAL:
[ConnectionManager] * Config db.defaultconfiguration - Error from db.defaultconfiguration.defaultservergroup (primary): BROKER : ** This process terminated with exit code 2. (8619)] (ADMMsg005)
GOAL:
[ConnectionManager] * Config <config> - Error from <servergroup>: BROKER : ** This process terminated with exit code <n>. (8619)] (ADMMsg005)
FACT(s) (Environment):
OpenEdge 10.x
Progress 9.x
All Supported Operating Systems
FIX:
The error message 8619 is a generic message which indicates that the database broker process failed immediately upon startup by the AdminServer database plug-in. It does not carry any information about the reason why the broker failed to start.
In order to get more information, it is therefore necessary to troubleshoot the behavior of the database broker itself. Since the database messages are not output to the AdminServer log file, the following steps are necessary:
1. look at the database log file (.lg). In most cases the database broker would display more information about the failure in that file.
2. start the database broker manually on the command line prompt, using the same exact command line used by the AdminServer. This will allow the broker to display any error message (if applicable) on the console, including any messages not reported to the database log.
The command line used by AdminServer is usually reported on the line as message (7402) immediately prior to error 8619 in the AdminServer log file. This is an example of such a message:
[ConnectionManager] Command = [DLC\bin\_mprosrv, -classpath, "DLC/java/ext/jmxri.jar;DLC/java/ext/mgmt_agent.jar;DLC/java/ext/mgmt_client.jar;DLC/java/ext/mgmt_config.jar;
DLC/java/ext/sonic_Client.jar;DLC/java/progress.jar;DLC/java/osmetrics.jar;DLC/java/jdbc.jar;DLC/java/base.jar;DLC/java/openedge.jar;DLC/java/util.jar;DLC/java/ext/soap.jar;DLC/java/prorepl.jar;
DLC/java/ext/wsdl4j.jar", -properties, "DLC/properties/conmgr.properties", -servergroup, db.defaultconfiguration.defaultservergroup, -adminport, 7839, -basetable, 1, -shmsegsize, 128, -tablerangesize, 1500, -indexrangesize, 3500, -m5] (7402)
To use the command line from the AdminServer log file, do as follows:
- take the string enclosed between brackets ([ ... ]), remove the brackets
- replace the commas by spaces
- paste the result on the command line, ensuring that the current working directory of the prompt is the working directory of the Progress/OpenEdge installation.
This will cause the broker to start "as if" it was started by the AdminServer while allowing to see more details about its startup.