*
The moose likes Websphere and the fly likes problem starting up WAS AE 4.0.5 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "problem starting up WAS AE 4.0.5" Watch "problem starting up WAS AE 4.0.5" New topic
Author

problem starting up WAS AE 4.0.5

david chan
Ranch Hand

Joined: Jun 10, 2002
Posts: 46
Hi,
I just install WAS AE 4.0.1 then apply the fix pack 4.0.5 (repository DB is Oracle 9i), then restart my win2000, and then type "adminserver.bat" in command prompt, it failed with this error, any idea?
===begin error mesg =====
[8/25/03 18:41:55:049 EDT] 6d13703a SystemOut U NMSV0012E: Name server initi
alization failed. Cannot create the CosNaming name tree.
javax.naming.NamingException: Caught unexpected exception, name=nodeRoots. Root
exception is org.omg.CORBA.INV_OBJREF: Resolving a context which has been destr
oyed. minor code: 0 completed: No
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.do_resolve_complete_i
nfo(WsnOptimizedNamingImpl.java:855)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete
_info(WsnOptimizedNamingImplBase.java:809)
at com.ibm.ws.naming.cosbase.WsnCosTreeInitializer.getNamingContext(WsnC
osTreeInitializer.java:145)
at com.ibm.ws.naming.cosbase.WsnCosTreeInitializer.createUpperTreeStruct
ure(WsnCosTreeInitializer.java:84)
at com.ibm.ws.naming.bootstrap.NameServer.createCosUpperTreeStructure(Na
meServer.java:391)
at com.ibm.ws.naming.bootstrap.NameServer.completeRdbCosInitialization(N
ameServer.java:509)
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.ifNSBeanHomeHackTheBi
nd(WsnOptimizedNamingImpl.java:1145)
.....
----- Begin backtrace for rootCause
org.omg.CORBA.INV_OBJREF: Resolving a context which has been destroyed. minor c
ode: 0 completed: No
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.do_resolve_complete_i
nfo(WsnOptimizedNamingImpl.java:855)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete
_info(WsnOptimizedNamingImplBase.java:809)
at com.ibm.ws.naming.cosbase.WsnCosTreeInitializer.getNamingContext(WsnC
osTreeInitializer.java:145)
at com.ibm.ws.naming.cosbase.WsnCosTreeInitializer.createUpperTreeStruct
ure(WsnCosTreeInitializer.java:84)
at com.ibm.ws.naming.bootstrap.NameServer.createCosUpperTreeStructure(Na
meServer.java:391)
at com.ibm.ws.naming.bootstrap.NameServer.completeRdbCosInitialization(N
ameServer.java:509)
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.ifNSBeanHomeHackTheBi
nd(WsnOptimizedNamingImpl.java:1145)
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.do_rebind_corba_objec
t(WsnOptimizedNamingImpl.java:497)
at com.ibm.ws.naming.rdbcos.WsnOptimizedNamingImpl.do_rebind_corba_objec
t(WsnOptimizedNamingImpl.java:497)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.rebind_corba_obj
.......
==== end truncated error mesg ===
Thanks.
David
Nagendra Prasad
Ranch Hand

Joined: Jul 11, 2002
Posts: 219
David,
Are you sure it is not a memory issue on the machine. Oracle 9i and WAS on the same box could be a cause. Is it possible to install WebSphere on a separate machine and then try the same operation.. it might offer a clue.


Best Regards,<br />Nagendra Prasad.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: problem starting up WAS AE 4.0.5
 
Similar Threads
about the install of websphere.
CORBA.OBJECT_NOT_EXIST
WAS 4 Initialization problem
Error : WSVR0068E: Attempt to start EnterpriseBean
Failure to start admin server