Solved

Naming Service unavailable WebSphere 4.0.6

Posted on 2004-08-11
11
432 Views
Last Modified: 2013-12-10
While starting the Application Server, I am getting the following error, anybody is there to help???


[8/11/04 20:06:17:961 GMT+05:00] 1ec4ed WsnInitCtxFac W NMSV0603E: Naming Service unavailable. Could not get the root context.


[8/11/04 20:06:18:029 GMT+05:00] 1ec4ed Jts U Unable to register transaction factory


javax.naming.ServiceUnavailableException: Caught exception when resolving initial reference=NameService. Root exception is org.omg.CORBA.INTERNAL: minor code: 0 completed: No


at com.ibm.CORBA.iiop.RIs.iterateClientResponsePostRIs(RIs.java:377)


at com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:484)


at com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:591)


at com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:355)


at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1877)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:437)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:363)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:229)


at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)


at com.ibm.ws.naming.util.WsnInitCtx.(WsnInitCtx.java:79)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:137)


at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)


at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)


at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)


at javax.naming.InitialContext.init(InitialContext.java:217)


at javax.naming.InitialContext.(InitialContext.java:193)


at com.ibm.ejs.jts.jts.Jts.bindTransactionFactory(Jts.java:206)


at com.ibm.ws.runtime.Server.initializeTranFactory(Server.java:1640)


at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:951)


at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime0(ManagedServer.java:408)


at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:884)


at com.ibm.ejs.sm.server.ManagedServer.main(ManagedServer.java:168)


at java.lang.reflect.Method.invoke(Native Method)


at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)


----- Begin backtrace for rootCause


org.omg.CORBA.INTERNAL: minor code: 0 completed: No


at com.ibm.CORBA.iiop.RIs.iterateClientResponsePostRIs(RIs.java:377)


at com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:484)


at com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:591)


at com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:355)


at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1877)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:437)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:363)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:229)


at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)


at com.ibm.ws.naming.util.WsnInitCtx.(WsnInitCtx.java:79)


at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:137)


at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)


at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)


at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)


at javax.naming.InitialContext.init(InitialContext.java:217)


at javax.naming.InitialContext.(InitialContext.java:193)


at com.ibm.ejs.jts.jts.Jts.bindTransactionFactory(Jts.java:206)


at com.ibm.ws.runtime.Server.initializeTranFactory(Server.java:1640)


at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:951)


at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime0(ManagedServer.java:408)


at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:884)


at com.ibm.ejs.sm.server.ManagedServer.main(ManagedServer.java:168)


at java.lang.reflect.Method.invoke(Native Method)


at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
0
Comment
Question by:kulsmadya
  • 4
  • 3
  • 2
  • +1
11 Comments
 
LVL 7

Expert Comment

by:damonf
ID: 11774962
need a bit more info.  What platform are you on?  Are you doing something special like using a different ORB, running WAS as a non-root user?  
0
 

Author Comment

by:kulsmadya
ID: 11780037
The websphere is installed on Sun Solaris 5.8.
WAS is running as root user only.

0
 
LVL 7

Expert Comment

by:damonf
ID: 11784105
With it running on Sun I was going to ask if you're running as root, which you are.  So much for that.  If you haven't made any changes to the ORB configuration, I'm not sure what to suggest.  IBM suggests looking at "other trace output" to determine root cause, but I don't see anything else useful in your stack trace.
0
 
LVL 23

Expert Comment

by:rama_krishna580
ID: 11827317
Hi,

If the application uses it own name service, which possible, than it must be a way to pass it the ORB details via system proerty or a property file. In addition, you need to make the ORB jar files in the class path.
YOU DONT NEED to change WAS name service.

For detailed Error/Solution info, look at here...
http://www-306.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/04070203.html

And specifically....

Explanation      :   This exception occurs when you specify an invalid host server name.
Possible causes:   Incorrect host server invoked , Invalid host server name
Run the launchClient command again and specify the correct name of your host server with the -CCBootstrapHost parameter.

i hope it may help you

R.K
0
 

Author Comment

by:kulsmadya
ID: 11880387
I got the answer for this problem.

The loghost entry for the node name was missing from /etc/hosts file.
Added the same and its working fine.


0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:kulsmadya
ID: 11880397
how do I close this question??
0
 
LVL 23

Expert Comment

by:rama_krishna580
ID: 11880479
Hi,

Have you looked at my answer, thats what i mentioned...that some thing wrong with your host server/HOST.
so check it out for more info.

R.K
0
 

Author Comment

by:kulsmadya
ID: 11882683
The launchClient didnt help me as the host name was mentioned in the hosts file.

The loghost was not mentioned in the hosts file along with the node name.

0
 
LVL 7

Expert Comment

by:damonf
ID: 11892322
If you feel like you answered your own question and want the points back, post a Q in Community Support forum.

Cheers,

damonf
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 12222148
PAQed, with points refunded (500)

Computer101
E-E Admin
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

This exercise is about for the following scenario: Dmgr and One node with 2 application server. Each application server contains it owns application. Application server name as follows server1 contains app1 server2 contains app1 Prereq…
Upgrading Tomcat – There are a couple of methods to upgrade Tomcat is to use The Apache Installer is to download and unzip and run the services.bat remove|install Tomcat6 Because of the App that we are working with, we can only use Tomcat 6.…
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now