javax.naming.NameNotFoundException: env not bound in JBoss EAP

Solution Unverified - Updated -

Issue

  • Our application is failing to lookup an object in JNDI with this exception in JBoss EAP 5
Caused by: javax.naming.NameNotFoundException: env not bound
                at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
                at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
                at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
                at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:753)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:880)
                at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
                at javax.naming.InitialContext.lookup(InitialContext.java:411)
                ...

Environment

Red Hat JBoss Enterprise Application Platform (EAP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.