5 Replies Latest reply on Jun 18, 2010 11:55 AM by jboss q

    Jboss 5.1 and ejb 2.1

    Rukmini V Newbie

       

      Hello

      i am getting the following error when running my application on jboss 5.1. i am using ejb2.1

       

       

      com.sbc.adcis.gui.exceptions.WorkerException

      [06/17/10 03:23 PM EDT]

      [06/17/10 03:23 PM EDT] Worker.getRemoteInterface( ):

      javax.naming.NameNotFoundException: ADCIS2 not bound

       

      at com.sbc.adcis.gui.workers.Worker.getRemoteInterface(

      Worker.java:496)

      at com.sbc.adcis.gui.workers.LoginWorker.executeEJBMethod(

      LoginWorker.java:50)

      at com.sbc.adcis.gui.workers.Worker.executeWrappedEJBMethod(

      Worker.java:572)

      at com.sbc.adcis.gui.workers.LoginWorker.runWorker(

      LoginWorker.java:39)

      at com.sbc.adcis.gui.workers.Worker.run(

      Worker.java:147)

      [06/17/10 03:23 PM EDT] LogoutWorker.executeWrappedEJBMethod( ): Calling EJB from LogoutWorker: com.sbc.adcis.gui.workers.LogoutWorker

      [06/17/10 03:23 PM EDT] Worker.haveRemoteInterface( ): haveRemoteInterface returning: false

      [06/17/10 03:23 PM EDT] Client.logoutFinished( ): Application is terminating.

       

      Is it ok to use ejb 2.1 with jboss 5.1

       

       

      thanks

      Rukmini

       

       

        • 1. Re: Jboss 5.1 and ejb 2.1
          jboss q Newbie

          make sure your ejb has been deployed correctly. if so, you may check the ejb jndi name used in the client code by the jndi view

          • 2. Re: Jboss 5.1 and ejb 2.1
            Rukmini V Newbie

            The same ear is working fine with jboss4.3 . We have no issues with jndi binding.

            We are migrating to jboss 5.1 that is where we are seeing the issue

            • 3. Re: Jboss 5.1 and ejb 2.1
              jaikiran pai Master

              These logs look like client side logs. Please check the server side logs to check if there is any exception. Also please use the JNDIView in jmx-console to check the jndi name for your deployed beans.

              • 4. Re: Jboss 5.1 and ejb 2.1
                Rukmini V Newbie

                The bound issue was resolved the ear was not deployed correctly but now once the ear is deployed i am recieving this error . There are no errors in the server logs. i cant find this class in any of the jars in the jboss 5.1

                 

                 

                [06/18/10 10:41 AM EDT] Worker.getRemoteInterface( ):

                javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.proxy.ejb.SecurityContextInterceptor (no security manager: RMI class loader disabled)]

                com.sbc.adcis.gui.exceptions.WorkerException

                at com.sbc.adcis.gui.workers.Worker.getRemoteInterface(

                Worker.java:496)

                at com.sbc.adcis.gui.workers.LoginWorker.executeEJBMethod(

                LoginWorker.java:50)

                at com.sbc.adcis.gui.workers.Worker.executeWrappedEJBMethod(

                Worker.java:572)

                at com.sbc.adcis.gui.workers.LoginWorker.runWorker(

                LoginWorker.java:39)

                at com.sbc.adcis.gui.workers.Worker.run(

                Worker.java:147)

                [06/18/10 10:41 AM EDT] LogoutWorker.executeWrappedEJBMethod( ): Calling EJB from LogoutWorker: com.sbc.adcis.gui.workers.LogoutWorker

                [06/18/10 10:41 AM EDT] Worker.haveRemoteInterface( ): haveRemoteInterface returning: false

                [06/18/10 10:41 AM EDT] Client.logoutFinished( ): Application is terminating.

                • 5. Re: Jboss 5.1 and ejb 2.1
                  jboss q Newbie

                  the org.jboss.proxy.ejb.SecurityContextInterceptor class is in the jboss-client.jar of jboss 5.1, so i guess you use the earlier verion of jboss-client.jar