4 Replies Latest reply on Sep 9, 2002 8:33 PM by Michael

    javax.naming.NameNotFoundException:

    Michael Newbie

      I'm trying to deploy a simple SFSB in JBoss3.0. but I'm getting
      the following error from my client.

      Starting TestMySqlDSSessionBean
      javax.naming.NameNotFoundException: TestMySqlDSSession not bound

      I checked the following JNDI entries by way of the following instructions
      -----------------------
      http://localhost:8082
      service=JNDIView
      click on list
      ----------------------
      I do not see the particular ejb jar that I believe got correctly deployed in the default/deploy directory
      see below.

      20:15:05,730 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
      -3.0.0_tomcat-4.0.3/server/default/deploy/ejb-testMySqlDS.jar
      20:15:05,730 INFO [Server] JBoss (MX MicroKernel) [3.0.0 Date:200205311035] Sta
      rted in 3m:47s:940ms
      20:15:05,840 INFO [MainDeployer] Successfully completed deployment of package:
      file:/C:/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/ejb-testMySqlDS.jar

      Why is JBoss not recognizing this correctly. Its probably why I get the error

      -- Any ideas?

        • 1. Re: javax.naming.NameNotFoundException:
          mBird Newbie

          Do you have the JBoss jars and JNDI correct --

          Try copy/paste the below and name it run.bat (in the last line java -cp %myCLASSPATH% %myD% client change client to whatever your client's name is):

          Looks sloppy here but if you cut/paste into text editor will look normal (this is Windows version but you can adapt for UNIX if needed):

          set myCLASSPATH=%CLASSPATH%;.;%JBOSS_DIST%\client\concurrent.jar;%JBOSS_DIST%\client\gnu-regexp.jar;%JBOSS_DIST%\client\jaas.jar;%JBOSS_DIST%\client\jacorb.jar;%JBOSS_DIST%\client\jboss-client.jar;%JBOSS_DIST%\client\jboss-common-client.jar;%JBOSS_DIST%\client\jboss-iiop-client.jar;%JBOSS_DIST%\client\jboss-j2ee.jar;%JBOSS_DIST%\client\jboss-jsr77.jar;%JBOSS_DIST%\client\jboss-net-client.jar;%JBOSS_DIST%\client\jboss-system-client.jar;jars\jbossha-client.jar;%JBOSS_DIST%\client\jbossmq-client.jar;jars\jbossmqha.jar;jars\jbosssx-client.jar;jars\jcert.jar;jars\jmx-connector-client-factory.jar;jars\jmx-ejb-connector-client.jar;jars\jmx-rmi-connector-client.jar;jars\jnet.jar;jars\jnp-client.jar;jars\jsse.jar;jars\log4j.jar
          set myD=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.provider.url=localhost:1099 -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
          java -cp %myCLASSPATH% %myD% client
          pause

          • 2. Re: javax.naming.NameNotFoundException:
            Juan Jesus Tova Ruiz Newbie

            The log you have posted doesn't has any reference to EJBModule. That is when you deploy an ejb corretly the EJBModule logs a message whith the ejb name.
            It looks like if the jar file doesn't has the deployment descriptor files corretly. Check the META-INF directory and the deployment descriptors in the jar file.

            • 3. Re: javax.naming.NameNotFoundException:
              Michael Newbie

              Right on Juan. Yes that was my problem I must have had some erroneous files in my META-INF.
              I didn't even have the entries display in the log for the EJBModule like you said, and now I do.
              I now can build and deploy correctly.

              Thanks for the responses guys, Its refreshing to not only get feedback vut good suggestions as well.

              • 4. Re: javax.naming.NameNotFoundException:
                Michael Newbie

                I've been trying to post this reply
                but Hopefully this went through.

                Juan you were right on. I must have had some bad files left over in my META-INF. I recreated my ejb-jar and jboss .xml files. I was then able to build and deploy
                my jar files.

                I now see my EJBModule come up during startup, correctly
                displaying my EJB

                Thanks to both responses. Its nice seeing questions get answered with great things to try.