Kbase 22094: Invalid Entry in ubroker.properties Causes Errors on Start
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/3/2002 |
|
SUMMARY:
This Solution summarizes some symptoms you will experience when there is an invalid entry for the Unified Broker in the ubroker.properties file. This information can also be helpful when troubleshooting similar problems.
EXPLANATION:
When there is an invalid entry (i.e., xxx=yyy) in the ubroker.properties file and you attempt to start a broker that is defined after the invalid entry, the messages received are not particularly illuminating.
Connecting to Progress AdminServer using
rmi://localhost:20931/Chimera (8280)
Searching for wsbroker1 (8288)
Unable to connect to wsbroker1 (8289)
Unable to find wsbroker1 (8281)
In this case, there is an invalid entry for wsbroker2 which is defined before wsbroker1. Using the wsconfig utility to validate entries for wsbroker2, you will find that any modifications after the invalid one are not taken by the AdminServer.
SOLUTION:
Carefully compare what is defined in the ubroker.properties file with what is displayed by the wsconfig utility. Make sure every entry in the Unified Broker definitions is valid.
NOTE: agent_retry_val, introduced by Progress Knowledge Base Solution 21009, should be defined in the environment section for the broker, not directly in the ubroker section.
References to Written Documentation:
Progress Knowledge Base Solution 21009, "WebWrite() error 6404"