This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Websphere and the fly likes MQSeries, JMS, WebSphere Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "MQSeries, JMS, WebSphere" Watch "MQSeries, JMS, WebSphere" New topic
Author

MQSeries, JMS, WebSphere

Richard Hu
Greenhorn

Joined: May 27, 2002
Posts: 5
Could anybody give me a help? When I tried to run JMSAdmin with JMSAdmin.config with the following configuration:
INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
PROVIDER_URL=iiop://localhost:900
there are some exception as following:
07:02:06 [1034204526592] [P=523608 =0:CT] com.ibm.mq.jms.admin.JMSAdmin@ee3914 constructor() javax.naming.ServiceUnavailableException exception caught: NULL returned when resolving initial reference=NameService
javax.naming.ServiceUnavailableException: NULL returned when resolving initial reference=NameService
at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:452)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:337)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:200)
at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)
at com.ibm.ejs.ns.jndi.CNInitialContextFactory.getInitialContext(CNInitialContextFactory.java:68)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
at com.ibm.mq.jms.admin.AdminService.initJNDI(AdminService.java:187)
at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:229)
at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1818)
07:02:06 [1034204526602] [P=523608 =0:CT] com.ibm.mq.jms.admin.JMSAdmin@ee3914 Unable to initialise JNDI. Calling System.exit()

I Have websphere 4 Advanced Server Edition, and MQSeries5.2.
Thanks for any suggestions.


SCJP2<br />SCWCD<br />BEA Certified Specialist: Server
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
I have to ask -- have you started the WebSphere admin service prior to running JMSAdmin? Did you verify that it was in fact, running?
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Richard Hu
Greenhorn

Joined: May 27, 2002
Posts: 5
Thanks, Kyle. I've start WebSphere Admin Service in my Windows2000. I also tried to stop and start the WebSphere Service. I tried use the command:
netstat -a
to check the 900 port. There is one process is listenning on port 900. I don't know how to check the configuration of iiop naming service in websphere, how to make sure it's configured right and running well.
From the exception information, it seems that the naming service is not running. Do you have any suggestion about it? Thanks.
Regards,
Richard
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Well, the way to determine if the naming service is running is to check the WebSphere system log and make sure that the admin service started correctly. If there are any errors in the log, it's probably not working.
Kyle
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: MQSeries, JMS, WebSphere
 
Similar Threads
Naming Service unavailable
Kyle, Tony- -ServiceUnavailableException while looking context from Remote host
was4 connection erro with db2(urgent!!!!)
JMSAdmin tool problem
Naming Service unavailable WebSphere 4.0.6