Kbase 21486: Adminserver/AS/WS die with long PROPATH
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
SUMMARY:
Setting the long PROPATH (> 1000 bytes) in the 9.1C AppServer/WS's agent's PROPATH property of the ubroker.properties and then querying the status of the running broker might cause the AdminServer to die or the broker itself to crash. This problem is manifested with both WebSpeed and AppServer brokers. There are no messages in the admserv.log file or exceptions whatsoever (apart from adc0.exp with the Progress Explorer). In WebSpeed server log file you might see memory violation sporadically.
In the Progress Explorer you would see the error message:
Lost connection to AdminServer on <hostname>. Please verify it is running. (9172)
Depending on the OS, in the AppServer log file you would see:
Win 2000 - no messages
Solaris 5.7 - Message in the AppServer server log file:
11:25:57 05 Sep 2001 Application Server 2989 Specified name too long: (and the content of the propath)
Linux Red Hat - error message in the server log:
** "v" was not found. (293)
v startup procedure ended with an ERROR condition. (8025)
Querying the status through Progress Explorer does not cause the AdminServer to crash. Customers using the Explorer tool may notice that the AppServer Broker reports back a live status (Right mouse click -> Status). However, a status check on the NameServer shows no AppServer Broker as being registered. The AppServer Broker can be stopped, it's PROPATH reduced, and restarted. It will then register with the NameServer and be fully functional.
EXPLANATION:
There seams to be a problem with AdminServer handling the entry that has value greater than 1031 bytes.This has been logged as the bug #20010905-003. Versions prior to 9.1C have a PROPATH buffer limit of 1k. Version 9.1D will increase that limit to 4k.
SOLUTION:
The workaround for this problem is to have PROPATH with the total lenght less than 1031 bytes.