1 Reply Latest reply on Mar 6, 2003 9:58 AM by andyc

    External Context lookup problem in 3.0.6

    andyc

      I have recently upgraded from Jboss 2.4.6 to 3.0.6. I am now having a problem with lookups on an External Context. I use this context to lookup my MQ Series Queue Connection Factory and Queues. In 2.4.6 I specified the following in the jboss.jcml file:


      external/fs
      external.fs.props
      javax.naming.InitialContext


      In 3.0.6 I created a file called external-naming-service.xml in the deploy directory. It looks like this:


      external/fs
      /conf/external.fs.props
      javax.naming.InitialContext


      I placed my external.fs.props file in the conf directory. It looks like this:

      java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
      java.naming.provider.url=file:///usr/local/jndi/jms

      The following code works fine in my 2.4.6 servlet but not in 3.0.6

      InitialContext twbctx = new InitialContext();
      Context fsCtx = (Context) twbctx.lookup("external/fs");
      m_Factory = (QueueConnectionFactory) fsCtx.lookup("twblite_qcf");

      m_Queue = (Queue) fsCtx.lookup("queue/" + "twblite");

      I now receive a NamingNotFoundException trying to do lookups.

      I have also noticed that in 2.4.6, the JNDIView displays the entire contents under external/fs whereas in 3.0.6 it does not.

      I have check through the documentation but cannot figure this out.

      Any help would be appreciated.

      Andy

        • 1. Re: External Context lookup problem in 3.0.6
          andyc

          I found my answer in the posting "Re: Cannot see external context in JNDI namespace Posted: Nov 8, 2002 11:42 AM"

          Things are working fine now. This problem was one of several configuration challenges I encountered in upgrading from 2.4.6 to 3.0.x. Does anyone know of a migration document that lists things to look out for when upgrading?