JNDI Context problem

[Ram Kas]

When I try to do a lookup of JMS Queue , I get the following error:

Could not create JNDI API context: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory [Root exception is java.lang.ClassNotFoundException: com.ibm.websphere.naming.WsnInitialContextFactory]

My Code is as follows:

  try {
        Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809/");
//initialContext =  new InitialContext(env);
            jndiContext = (Context) new InitialContext(env);
        } catch (NamingException e) {
            System.out.println("Could not create JNDI API " +
                "context: " + e.toString());
            System.exit(1);
        }
        
        /* 
         * Look up connection factory and queue.  If either does
         * not exist, exit.
         */
        try {
            queueConnectionFactory = (QueueConnectionFactory)
                jndiContext.lookup("QueueConnectionFactory");
            queue = (Queue) jndiContext.lookup(queueName);
        } catch (NamingException e) {
            System.out.println("JNDI API lookup failed: " + 
                e.toString());
            System.exit(1);
        }  

Can any body let me know where I am going wrong? Do I need to set any classpath for it to work?

Thanks
Dinakar.K

[Cameron Wallace McKenzie]

The jar containing this file seems to not be on your classpath:

com.ibm.websphere.naming.WsnInitialContextFactory

Find that class, and you should be good.

-Cameron McKenzie

[Ravi Nikam]

Which server version you are using there? if 6.1 then check properties might be you need this :

< !-- IBM ORB Properties -->
property name="org.omg.CORBA.ORBClass" value="com.ibm.CORBA.iiop.ORB"

else check for that perticular class and load thar JAR to classpath.

good luck ...
[ January 30, 2008: Message edited by: Ravi Nikam ]

[Francesco Bellini]

Hello,

I have this problem too, and I am trying to configure WAS 6 and 7 to use Apache ActiveMQ to create and use a Queue.
The code I am using is pretty similar to the one posted here in the first post, and I get an error when the code reaches this line:

queue = (Queue) jndiContext.lookup("jms/systemMessageQueue");

This is the error:

com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.
Reference object. [Root exception is javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable 
{java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQWASInitialContextFactory, com.ibm.websphere.naming.hostname.normalizer=
com.ibm.ws.naming.util.DefaultHostnameNormalizer, com.ibm.websphere.naming.name.syntax=jndi, com.ibm.websphere.naming.namespace.connection=eager, 
com.ibm.ws.naming.ldap.ldapinitctxfactory=com.sun.jndi.ldap.LdapCtxFactory, com.ibm.websphere.naming.jndicache.cacheobject=populated, 
com.ibm.websphere.naming.namespaceroot=defaultroot, com.ibm.ws.naming.implementation=WsnIpCos, com.ibm.ws.naming.wsn.factory.initial=
com.ibm.ws.naming.util.WsnInitCtxFactory, com.ibm.websphere.naming.jndicache.maxcachelife=0, com.ibm.websphere.naming.jndicache.maxentrylife=0, 
java.naming.connectionFactoryNames=jms/queueConnectionFactory, java.naming.provider.url=tcp://localhost:61616, 
com.ibm.websphere.naming.jndicache.cachename=providerURL, java.naming.factory.url.pkgs=com.ibm.ws.naming:com.ibm.ws.runtime:
com.ibm.iscportal.jndi:com.ibm.ws.naming:com.ibm.ws.naming, java.naming.queue=jms/systemMessageQueue} [Root exception is 
java.lang.StringIndexOutOfBoundsException: String index out of range: 18]]

The code above runs on Websphere where I have defined a QueueConnectionFactory and a Queue named "jms/systemMessageQueue" which exists on ActiveMQ (up and running).

I really don't understand why this happens, even if I tried to add the jar file to the classpath as suggested.

Can somebody help me please?

[Marcos Maia]

You need to add MQ client jars to your app classpath. You can find some MQ client jars inside the MQ connector in WebSphere at ${WEBSPHERE_HOME}/AppServer/installedConnectors the MQ libs are inside the .rar file called: wmq.jmsra.rar

[Francesco Bellini]

Ok, it seems that it was a bug of activemq. The snapshot version 5.8.0 seems to be bug free as regard such problem.