4 Replies Latest reply on Nov 19, 2013 8:53 AM by shar machireddy

    how to resolve ejb jndi naming issue while migrating from jboss 5 to jboss as 7?

    shar machireddy Newbie

      13:15:14,944 INFO  [javax.enterprise.resource.webservices.rpc.server.http] (ServerService Thread Pool -- 75) JAXRPCSERVLET15: JAX-RPC servlet destroyed

      13:15:14,954 INFO  [javax.enterprise.resource.webservices.rpc.server.http] (ServerService Thread Pool -- 75) JAXRPCSERVLET13: JAX-RPC context listener destroyed

      13:15:14,959 INFO  [stdout] (ServerService Thread Pool -- 80) javax.naming.InitialContext@38fbbfd

       

       

      13:15:14,974 ERROR [com.eds.as.web.servlet.MBeanStartupServlet] (ServerService Thread Pool -- 80) Unable to perform lookup NamingException: javax.naming.NameNotFoundException: global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal -- service jboss.naming.context.java.jboss.exported.global.eds-fares-direct-intg.timer-ejb."com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal"

        at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103)

        at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)

        at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174)

        at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) [jboss-client.jar:7.2.0.Final-redhat-8]

        at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) [jboss-client.jar:7.2.0.Final-redhat-8]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

       

      13:15:18,051 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry ../../../opt/SUNWjax/share/lib/FastInfoset.jar in /C:/Jboss/jboss-eap-6.1/bin/content/eds-fares-direct-intg.ear/APP-INF/lib/jaxrpc-impl.jar  does not point to a valid jar for a Class-Path reference.

       

      13:15:18,735 INFO  [stdout] (ServerService Thread Pool -- 79) javax.naming.InitialContext@285b777d

       

       

      13:15:18,896 INFO  [javax.enterprise.resource.webservices.rpc.server.http] (ServerService Thread Pool -- 85) JAXRPCSERVLET14: JAX-RPC servlet initializing

      13:15:18,944 ERROR [com.eds.as.web.servlet.MBeanStartupServlet] (ServerService Thread Pool -- 79) Unable to perform lookup NamingException: javax.naming.NameNotFoundException: global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal -- service jboss.naming.context.java.jboss.exported.global.eds-fares-direct-intg.timer-ejb."com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal"

        at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103)

        at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)

        at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174)

        at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) [jboss-client.jar:7.2.0.Final-redhat-8]

        at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) [jboss-client.jar:7.2.0.Final-redhat-8]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

        • 1. Re: how to resolve ejb jndi naming issue while migrating from jboss 5 to jboss as 7?
          Philippe Marschall Expert

          The following name can not be found:

          global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal

          the correct name should be logged, likely something like:

          eds-fares-direct-intg/timer-ejb/TimerService!com.eds.as.ejb.timer.TimerServiceLocal

          • 2. Re: how to resolve ejb jndi naming issue while migrating from jboss 5 to jboss as 7?
            shar machireddy Newbie

            Thanks for your reply.

            I tried by using eds-fares-direct-intg/timer-ejb/TimerService!com.eds.as.ejb.timer.TimerServiceLocal then I got this error:

             

            15:56:06,985 INFO  [stdout] (ServerService Thread Pool -- 124) javax.naming.InitialContext@1c3ef093

             

             

            15:56:07,325 ERROR [com.eds.as.web.servlet.MBeanStartupServlet] (ServerService Thread Pool -- 124) Unable to perform lookup NamingException: javax.naming.NameNotFoundException: global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal -- service jboss.naming.context.java.jboss.exported.global.eds-fares-direct-intg.timer-ejb."com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal"

              at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103)

              at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)

              at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174)

              at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) [jboss-client.jar:7.2.0.Final-redhat-8]

              at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) [jboss-client.jar:7.2.0.Final-redhat-8]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

              at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

            • 3. Re: how to resolve ejb jndi naming issue while migrating from jboss 5 to jboss as 7?
              Philippe Marschall Expert

              The JNDI names should be logged in the console when the server starts/the application deploys. Can you post this log?

              • 4. Re: how to resolve ejb jndi naming issue while migrating from jboss 5 to jboss as 7?
                shar machireddy Newbie

                19:12:24,760 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named com.eds.as.ejb.timer.TimerService in deployment unit subdeployment "timer-ejb.jar" of deployment "eds-fares-direct-intg.ear" are as follows:

                 

                 

                  java:global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal

                  java:app/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal

                  java:module/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocal

                  java:global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceRemote

                  java:app/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceRemote

                  java:module/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceRemote

                  java:jboss/exported/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceRemote

                  java:global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceHome

                  java:app/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceHome

                  java:module/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceHome

                  java:jboss/exported/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceHome

                  java:global/eds-fares-direct-intg/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocalHome

                  java:app/timer-ejb/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocalHome

                  java:module/com.eds.as.ejb.timer.TimerService!com.eds.as.ejb.timer.TimerServiceLocalHome

                 

                 

                these are the JNDIs I got in log