Stack trace from getting started

[siegfried1]

I downloaded http://umn.dl.sourceforge.net/sourceforge/jboss/JBoss.3.0QuickStart.Draft3.pdf and performed the build with no errors.

However, when I try to run the client, I get a stack trace. What am doing wrong?
Thanks,
Sieg
./run-client.bat
C:\j2sdk1.4.0_01\jre\bin\java.exe -classpath ".;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\concurrent.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\getopt.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\gnu-regexp.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jaas.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jacorb.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-common-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-iiop-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-j2ee.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-jsr77-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-net-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-system-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jboss-transaction-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jbossha-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jbossjmx-ant.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jbossmq-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jbossmqha.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jbosssx-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jcert.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jmx-connector-client-factory.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jmx-ejb-connector-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jmx-rmi-connector-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jnet.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jnp-client.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\jsse.jar;C:\jboss-3.1.0alpha_tomcat-4.0.4\client\log4j.jar;..\client\client-test.jar" test.client.TestClient
javax.naming.NameNotFoundException: test not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
at org.jnp.server.NamingServer.lookup(NamingServer.java:253)
at org.jnp.server.NamingServer.lookup(NamingServer.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:901)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:869)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at test.client.TestClient.main(TestClient.java:21)

[schaefera]

Hi

I would guess that the EJB is not properly deployed. If you use a newer JBoss (>= 3.0.2) then open the jmx-console on "http://localhost:8080/jmx-console" (otherwise the good old: http://localhost:8082).
Look for the MBean with name "JNDIView" and check in the "Global Namespace" (listed at the bottom) if you find the JNDI path to the EJB.

Have fun - Andy

[dhopkins]

I too was getting this error.

It seams that when I started the server with: run -C all
it would occur, but when I started it normally, just plain run, it worked..guessing some other service that was starting up with all flag, was causing the problem...