Kbase P155047: WebSpeed broker receives unexpected message from server at startup and immediately shuts down
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/01/2010 |
|
Status: Verified
SYMPTOM(s):
WebSpeed broker receives unexpected message from server at startup and immediately shuts down
The following messages are found in the broker log:
ServerSocketsIPC <operation> IOException : <IOException_string> : <IOExceptionMsg_string> (8127)
ServerSocketsIPC read() IOException : java.io.EOFException : NULL (8127)
ServerIPCException in <funcName> : <ServerIPCException_string>. (8119)
ServerIPCException in getServerIPCMsg() : ServerIPC error: ubServerSocketsIPC.read() IOException: null. (8119)
Exception unbinding broker (not bound) : <ExceptionMsg_string> (8525)
Exception unbinding broker (not bound) : <<server name>> (8525)
ubroker <ubrokerbuildinfo> done. (8041)
Unexpected msg from server :
version= 109
type= 1 UBTYPE_ADMIN
src= 0 DEFAULT_UBSRC
rq= 0x1 UBRQ_ADMIN
tlvBuflen= 0x0
rqExt= 0x0
rsp= 0x0 UBRSP_OK
rspExt= 0x0
src= 0
adRq= 4 ADRQ_SERVER_TERMINATE
rsp= 0 ADRSP_OK
msglen= 0
buflen= 0
ERROR: cannot start server. (8100)
The following messages are found in the server log:
(Procedure:'ipCheckFixEOF c:\openacc\eliv3060\app\util\ox_run.p' Line:199) ** "?"was not found. (293)
(Procedure:'ipSetPropath c:\openacc\eliv3060\app\util\ox_run.p' Line:277) ** "?"was not found. (293)
(Procedure:'ipSetPropath c:\openacc\eliv3060\app\util\ox_run.p' Line:277) ** "?"was not found. (293)
(Procedure:'ipSuper c:\openacc\eliv3060\app\util\ox_run.p' Line:309)util/ox_super.p Database open_x not connected. (1006)
FACT(s) (Environment):
Restarting after power failure
Servers for other brokers can start
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
Because of some missing files in the application configuration, the application could not connect to the database and terminated in such a way as to cause the server to terminate with the unexpected message. The broker could not understand the message from the server and shut itself down.
FIX:
Correct the application problems that are causing the server to terminate.