7 Replies Latest reply on Apr 18, 2014 9:48 AM by Daniele Bella

    JDBC jndi not find by application but server already bound

    Daniele Bella



      I have one server of 5 in the cluster, the application in this server cannot find one jdbc with this error:


      Caused By: javax.naming.NameNotFoundException: While trying to look up comp/env/jdbc/adesioni/DataSource in /app/webapp/fatturazione/269539357.; remaining name 'comp/env/jdbc/adesioni/DataSource'

              at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)

              at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)

              at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)

              at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)

              at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)

              at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)



      The application it's target on entire cluster and the other server doesn't have a problem.

      If I check the JNDI tree for this server I find the correct bound


      Binding Name: comp.env,jdbc.adesioni.DataSource


      I have already try to cancel the entire server and recreate it.