javax.naming.ServiceUnavailableException problem!

[Ivan Fomin]

Hello WebSphere folk!

We can't got InitialContext remoutly.
initialContaxtFactory = WsnInitialContextFactory or CNInitialContaxtFactory
both not working

Hashtable hashtable = (Hashtable)properties.clone();
hashtable.put("java.naming.factory.initial",
initialContextFactory);//see above
hashtable.put("java.naming.provider.url", providerURL);//
iiop://localhost:900
hashtable.put("java.naming.security.authentication",
authentication != 0 ? ((Object) (authentication != 1 ? ((Object)
(authentication != 2 ? null : "CRAM_MD5")) : "simple")) : "none"); //"none"
in real
hashtable.put("java.naming.referral", "throw");

ictx = new InitialContext(hashtable); here is exception

We got following problem:

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(WsnInitCtxFactor
y.java:337)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory
.java:200)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnIniti
alContextFactory.java:80)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at com.ibm.mq.jms.admin.AdminService.initJNDI(AdminService.java)
at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:126)
at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1176)
09:55:58 [1003906558885] [P=556912:O=0:CT]
com.ibm.mq.jms.admin.AdminService@632c2d <== initJNDI() exit
09:55:58 [1003906558885] [P=556912:O=0:CT]
com.ibm.mq.jms.admin.JMSAdmin@971afc constructor()
javax.naming.ServiceUnavailableException exception caught: NULL returned
when resolving initial reference=NameService

Does enybody know what is it?

Best Regards,
Ivan Fomin

[Jasen Halmes]

Are you using the same jdk that was is using? This is the error you get, I
think, if you try to connect using a different jdk. We made sure we were using
the installed version and the error went away...