weblogic.application.ModuleException: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.Catdat'. Resolved 'jdbc'; remaining name 'Catdat'
Searched on Google with the first line of a JAVA stack trace?
We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.
Recommended solutions based on your search
Solutions on the web
via Oracle Community by 2791455, 1 year ago
via Google Groups by Luis Miguel Moya Moirón, 1 year ago
via broadleafcommerce.org by Unknown author, 1 year ago
via Stack Overflow by J Hughes
, 1 year agovia Oracle Community by kroberts5683, 1 year ago
via Stack Overflow by mmc18
, 2 years agojavax.naming.NameNotFoundException: Unable to resolve 'jdbc.Catdat'. Resolved 'jdbc'; remaining name 'Catdat'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:253)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at cat.gencat.jociapostes.bus.config.HibernateConfig.getDataSource(HibernateConfig.java:72)