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 provide 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 outputted to the AdminServer log file, the following steps are necessary:
1. Look at the database log file (.lg).
In most cases, the database broker will 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 reported on the line as message (7402) immediately prior to error 8619 in the AdminServer log file. This is an example a database startup message from OpenEdge 11.7.4:
[Database] Command = [DLC\bin\_mprosrv,
-properties, "DLC\properties\conmgr.properties",
-servergroup, popo.defaultconfiguration.defaultservergroup,
-adminport, 7846,
-spin 5000
-m5,
-classpath, "DLC/java/progress.jar;DLC/java/osmetrics.jar;DLC/java/prorepl.jar;
DLC/java/ext/xercesImpl.jar;DLC/java/ext/xmlParserAPIs.jar;DLC/java/ext/soap.jar;
DLC/java/ext/wsdl4j.jar;DLC/java/ext/jettison-1.3.4.jar"]
(7402)To use the command line from the AdminServer log file:
- Take the string enclosed between brackets ([ ... ]), remove the brackets
- Replace the commas by spaces
- Open a PROENV shell and 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.
The classpath is not strictly needed, but may be the cause of the startup failure when started under the AdminServer.
Note that a broker started manually on the command line will be terminated when the user session that was used to start it ends.
