Kbase P104957: What does message 8128 mean?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/3/2008 |
|
Status: Verified
GOAL:
What does message 8128 mean?
GOAL:
Why can't I start broker but receive error 8128?
GOAL:
What does promsgs 8128 mean?
GOAL:
ServerSocketsIPC read() MsgFormatException : com.progress.ubroker.util.ubMsg$InvalidMsgVersionException: MsgFormat : MsgFormat : InvalidMsgVersion[got ver=() :expecting ver=()] (8128)
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
FIX:
When you see error 8128 proceeded by server thread number in broker log file but no error or any information in server log file, following has happened.
The broker failed to start because it could not start (at least) one of the agent processes correctly, this agent is the agent that the related thread number is pointing to. After each agent process is executed, each agent process is supposed to connect to the private listening socket of each server thread , and send an initialization message to the broker. In the case of broker not starting, "something bad" happened during the agent initialization, and somehow some garbage got sent to the broker instead of the initialization message. The server thread detected that the initialization message was corrupt (InvalidMsgVersionException), and terminated, causing the entire broker process to terminate.
Unfortunately the server log does not contain any info as to what went wrong. This can happen if the error condition occurs before the agent opens the log. If agents connect to database, consult database lg file for further information.