list JNDI bindings in default JBoss install from command line client

Discussion in 'Java' started by rwfields@yahoo.com, Jan 4, 2007.

  1. Guest

    Hello,

    I am trying to use JBoss 3.2.5 as a JNDI server. JBoss has a vanilla
    install on Gentoo Linux. The standard default server configuration is
    running unchanged. I attempt to execute the following program, only
    to see which bindings are available. Output and classpath follow the
    program listing. I have no idea why this is failing. Any suggestions
    would be much appreciated.

    Thanks,
    Randall

    ---

    import java.util.*;
    import javax.naming.*;

    public class JNDI {
    public static void main(String[] args) {
    try {
    Context ctx = new InitialContext();
    System.out.println("Printing environment keys:");
    Hashtable hash = ctx.getEnvironment();
    Enumeration keys = hash.keys();
    while ( keys.hasMoreElements() ) {
    Object key = keys.nextElement();
    Object value = hash.get(key);
    System.out.println(key + "=" + value);
    }
    ctx.listBindings(ctx.getNameInNamespace());
    }
    catch (Exception e) {
    e.printStackTrace();
    }
    }
    }

    ---

    OUTPUT:

    Printing environment keys:
    java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
    java.naming.provider.url=localhost:1099
    java.naming.factory.url.pkgs=org.jboss.naming:eek:rg.jnp.interfaces
    javax.naming.CommunicationException [Root exception is
    java.lang.ClassNotFoundException:
    org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory (no
    security manager: RMI class loader disabled)]
    at
    org.jnp.interfaces.NamingContext.listBindings(NamingContext.java:766)
    at
    org.jnp.interfaces.NamingContext.listBindings(NamingContext.java:737)
    at javax.naming.InitialContext.listBindings(InitialContext.java:406)
    at JNDI.main(JNDI.java:32)
    Caused by: java.lang.ClassNotFoundException:
    org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory (no
    security manager: RMI class loader disabled)
    at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371)
    at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
    at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
    at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
    at
    sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
    at
    java.io_ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
    at
    java.io_ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
    at
    java.io_ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
    at java.io_ObjectInputStream.readObject0(ObjectInputStream.java:1305)
    at java.io_ObjectInputStream.readObject(ObjectInputStream.java:348)
    at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
    at
    org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:30)
    at
    org.jnp.interfaces.NamingContext.listBindings(NamingContext.java:762)
    ... 3 more

    ---

    The classpath this program uses is simply all the jars in the jboss
    client directory:

    > echo $CLASSPATH

    ..:/usr/share/jboss/client/jbosssx-client.jar:/usr/share/jboss/client/jacorb.jar:/usr/share/jboss/client/jboss-common-client.jar:/usr/share/jboss/client/jmx-connector-client-factory.jar:/usr/share/jboss/client/jbosscx-client.jar:/usr/share/jboss/client/jboss-client.jar:/usr/share/jboss/client/jmx-client.jar:/usr/share/jboss/client/jsse.jar:/usr/share/jboss/client/jbossha-client.jar:/usr/share/jboss/client/jnet.jar:/usr/share/jboss/client/jboss-iiop-client.jar:/usr/share/jboss/client/avalon-framework.jar:/usr/share/jboss/client/jboss-net-client.jar:/usr/share/jboss/client/jnp-client.jar:/usr/share/jboss/client/jmx-ejb-connector-client.jar:/usr/share/jboss/client/log4j.jar:/usr/share/jboss/client/jboss-jaas.jar:/usr/share/jboss/client/gnu-regexp.jar:/usr/share/jboss/client/jmx-invoker-adaptor-client.jar:/usr/share/jboss/client/concurrent.jar:/usr/share/jboss/client/jmx-rmi-connector-client.jar:/usr/share/jboss/client/jbossall-client.jar:/usr/share/jboss/client/jboss-jsr77-client.jar:/usr/share/jboss/client/xdoclet-module-jboss-net.jar:/usr/share/jboss/client/getopt.jar:/usr/share/jboss/client/jboss-j2ee.jar:/usr/share/jboss/client/jbossmq-client.jar:/usr/share/jboss/client/jboss-transaction-client.jar:/usr/share/jboss/client/jcert.jar:/usr/share/jboss/client/jboss-system-client.jar
    , Jan 4, 2007
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Ofer Belinsky
    Replies:
    0
    Views:
    773
    Ofer Belinsky
    Jul 5, 2004
  2. Mike S
    Replies:
    0
    Views:
    23,000
    Mike S
    Sep 16, 2004
  3. Mick
    Replies:
    2
    Views:
    9,525
    Marcin Grunwald
    Feb 23, 2005
  4. Tim Terry

    jboss - tomcat JNDI problem

    Tim Terry, May 3, 2005, in forum: Java
    Replies:
    0
    Views:
    2,300
    Tim Terry
    May 3, 2005
  5. davout
    Replies:
    0
    Views:
    780
    davout
    May 12, 2005
Loading...

Share This Page