Kbase P119208: Error Initializing NameServer. (8193)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/24/2008 |
|
Status: Unverified
SYMPTOM(s):
Error Initializing NameServer. (8193)
Full log:
[06/10/02@10:31:58.250+0200] P-006112 T-main 1 --- --- C:\OpenEdge10B\WRK10B\NS1.ns.log opened.
[06/10/02@10:31:58.250+0200] P-006112 T-main 1 --- --- Logging level set to = 4
[06/10/02@10:31:58.250+0200] P-006112 T-main 1 --- --- Log entry types activated: NSPlumbing,
[06/10/02@10:31:58.281+0200] P-006112 T-main 2 NS NSPlumbing Starten NameServer NS1 rmi://host_name:20932/NS1 Port = 5164 Auszeit = 30. (8196)
[06/10/02@10:31:58.281+0200] P-006112 T-main 2 NS NSPlumbing Lastausgleich ermöglicht für NameServer NS1. (8199)
[06/10/02@10:32:21.812+0200] P-006112 T-main 1 NS NSPlumbing Fehler Registrierung NameServer NS1 mit RMI Registry rmi://host_name:20932/NS1 (8191)
[06/10/02@10:32:21.812+0200] P-006112 T-main 1 NS NSPlumbing Fehler Initialisierung NameServer. (8193)
FACT(s) (Environment):
ServicePack 10.0B05
Windows XP
OpenEdge 10.0B
CAUSE:
If the network name of your computer has an underscore in it (for example "pc_testoe10", this will trip up the nameserver (and possibly other processes) when trying to start it via the AdminServer. This is a known issue with jdk v1.4. See also:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5083594
FIX:
Workaround by using -Djava.rmi.server.hostname=ip_address or upgrade to OpenEdge version 10.1A or higher where we are using a different API call instead.