Kbase P108406: ODBC DataServer unified broker spawns a DataServer process but the process dies
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/09/2008 |
|
Status: Verified
SYMPTOM(s):
ODBC DataServer unified broker spawns a DataServer process but the process dies
The following errors are displayed in the broker log file:
IOException reading message from server : java.io.EOFException: pipe to server broken (8117)
ERROR: cannot start server. (8100)
admin error response received: 2. (8067)
Error No Servers available ... disconnecting client. (8091)
Ending serverPool thread: S-0001. (8077)
FACT(s) (Environment):
ODBC DataServer
Progress 9.1x
OpenEdge 10.0x
Windows NT 32 Intel/Windows 2000
Has both OpenEdge ODBC DataServer and OpenEdge Studio license installed in the machine
Have the PROSTARTUP environment variable setup for the unified broker in the ubroker.properties file
The -Mm parameter value is set for the unified broker in the ubroker.properties file
CAUSE:
Use of the PROSTARTUP environment variable with the unified broker is causing the DataServer process (_odbsrv) to terminate after broker starts it.
FIX:
Do not use the PROSTARTUP variable with the unified broker (odbbroker1). Instead use the -Mm parameter in the server startup parameter (srvrStartupParam) for the ODBC DataServer broker in the ubroker.propertes file as follows:
srvrStartupParam=-svub -S X -N TCP -U X -P X -hs 0 -s 40 -Mm 4096
After you start the broker, use the same value (stated in the ubroker.properties file as shown above) for the -Mm parameter on the 4GL/ABL client startup when connecting to the schema holder.