There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • weblogic.common.ResourceException: DataSource
    via by Unknown author,
  • db:: 3.86::Connection drop out issue with JMS 1k
    via by Unknown author,
  • db:: 3.84::JMS Deserialization Error ks
    via by Unknown author,
  • Error listening to Queue carnot Queue
    via by 259797,
    • javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/connect.jar#conn > ect/comp/env/user' Resolved: 'app/ejb/connect.jar#connect/comp/env' Unresolved: > 'user' ; remaining name 'user' > at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basi > > at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.ja > va:223) > at weblogic.jndi.internal.BasicNamingNode.lookup( > 87) > at weblogic.jndi.internal.BasicNamingNode.lookup( > 95) > at weblogic.jndi.internal.BasicNamingNode.lookup( > 95) > at weblogic.jndi.internal.WLContextImpl.lookup( > at weblogic.jndi.internal.WLContextImpl.lookup( > at > > at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext. > java:124) at javax.naming.InitialContext.lookup( at connect.InsertBean.setSessionContext(

    Users with the same issue

    Andreas Häber
    2 times, last one,
    Unknown visitor1 times, last one,