Kbase P42444: java.rmi.NotBoundException when using DBMan
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/09/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1X
SYMPTOM(s):
java.rmi.NotBoundException when using DBMan
Exception at Wed Aug 13 04:28:33 CEST 2003: java.rmi.NotBoundException
Message (excp): null
Stack Trace:
java.rmi.NotBoundException
at com.progress.common.rmiregistry.RegistryManager.lookupX (RegistryManager.java:368) (pc 106)
at com.progress.common.rmiregistry.RegistryManager.lookup(java.lang.String,java.lang.String,int) (RegistryManager.java:346) (pc 4)
at com.progress.common.rmiregistry.RegistryManager.lookup(java.lang.String) (RegistryManager.java:339) (pc 10)
at com.progress.chimera.clu.dbMan.dbMan.getJuniperPlugin (dbMan.java:676) (pc 70)
at com.progress.chimera.clu.dbMan.dbMan.<init> (dbMan.java:130) (pc 255)
at com.progress.chimera.clu.dbMan.dbMan.main (dbMan.java:72) (pc 5)
Wrong AdminServer port is being specified with dbman command
CAUSE:
This is a known issue
FIX:
Use correct port with dbman command
This expection does not cause any harm, as it happens only when (by mistake) the wrong port of AdminServer is specified with dbman command.