2 Replies Latest reply on Dec 13, 2004 8:19 AM by Dale Wyttenbach

    External File System JNDI problem

    specmurt Newbie

      I am trying to configure external file system JNDI (Sun reference implementation) to be accessible from JBoss 3.2.1. I created /JNDI folder and filled it with some definitions. Then I put the following in jboss-service.xml:
      ---

      external/fs
      external.fs.properties
      javax.naming.InitialContext

      ---
      My external.fs.properties is:
      ---
      java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
      java.naming.provider.url=file:///JNDI
      ---
      But it doesn't work. Then I use JNDIView it seems JBoss falls into infinite loop:
      +- UserTransaction
      +- invokers
      | +- pea
      | | +- pooled
      | | +- jrmp
      +- UUIDKeyGeneratorFactory
      +- UserTransactionSessionFactory
      +- external
      | +- fs (proxy: $Proxy10 implements interface javax.naming.Context)
      | | +- UserTransaction
      | | +- invokers
      | | | +- pea
      | | | | +- pooled
      | | | | +- jrmp
      | | +- UUIDKeyGeneratorFactory
      | | +- UserTransactionSessionFactory
      | | +- external
      | | | +- fs (proxy: $Proxy10 implements interface javax.naming.Context)
      | | | | +- UserTransaction
      | | | | +- invokers
      | | | | | +- pea
      | | | | | | +- pooled
      | | | | | | +- jrmp
      etc, etc, etc... (pea - is the network name of my computer)
      Can anybody help to resove this problem?

        • 1. Re: External File System JNDI problem
          Dale Wyttenbach Newbie

          I am currently experiencing the same behavior in jboss-3.2.3.

          In jboss-4.0.0, the behavior is slightly different: The JBoss VM appears to go into the infinite loop before any markup is returned.

          Is this a JNDIView bug, or a mis-use of ExternalContext config? In my case I added the following to server/default/conf/jboss-service.xml, immediately before the JNDIView MBean entry:

          <!-- Bind a remote LDAP server -->

          external/ldap/data
          external.ldap.data

          javax.naming.ldap.InitialLdapContext

          true

          • 2. Re: External File System JNDI problem
            Dale Wyttenbach Newbie

            I found out that the documentation I was reading is wrong. Use the PropertiesURL attribute in order to locate the external file that contains LDAP connection info, NOT Properties attribute as shown in the example.