Kbase P47112: OpenEdge 10 Nameserver fails to start due to invalid hostname
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/09/2008 |
|
Status: Verified
SYMPTOM(s):
NameServer fails to start
NameServer log shows following errors:
Error Registering NameServer <NameServer> with RMI Registry <URL> (8191)
Error Initializing NameServer. (8193)
AdminServer log shows following error:
SvcControlCmd.connectToService() failure: Unable to connect to the service process at rmi://xxxx:20931/NS1(after 10 retries) (8171)
NameServer fails to start even with default ubroker.properties.
FACT(s) (Environment):
OpenEdge 10.0x
All Supported Operating Systems
CAUSE:
Bug# 20031016-018
CAUSE:
In OpenEdge 10.0A, the JDK used was upgraded to jdk v1.4.
The newer JDK has a change in behavior that results in the Underscore or other non-standard characters in the system name/hostname stopping the RMI url from being resolved correctly.
FIX:
Upgrade to OpenEdge 10.1A or later. In the later releases, a workaround as suggested by SUN has been implemented.
Workarounds:
1) Rename computer using only standard characters - letters, numbers (0-9) and hyphens ("-")
2) for Windows, after changing the machine name, make sure that registry keys have the correct new name:
Hostname and NV Hostname in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters
3) Configure the AdminServer properties to include the java.rmi.server.hostname, using the IP address of the host instead of it's hostname:
- Stop the AdminService.
- Open the AdminServerPlugin.properties file in C:\Progress\OpenEdge\Properties.
- Modify the [PluginPolicy.Progress.AdminServer] section of your AdminServerPlugins.properties file and add -Djava.rmi.server.hostname=<IP ADDRESS> to the jvmargs= line.
[PluginPolicy.Progress.AdminServer]
classpath=<your Classpath info>
jvmargs=-Djava.rmi.server.hostname=<IP ADDRESS>
pluginclasspath=!{value-of:classpath}
- Save the file, restart the AdminService and then try to start up an AppServer.