javax.naming.NamingException

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.

    • javax.naming.NamingException: Cannot establish connection. at oracle.tip.tools.ide.fabric.asbrowser.SOARootContextProvider.listBindingsImpl(SOARootContextProvider.java:34) at oracle.rc.asadapter.context.spi.AbstractContextProvider.listBindings(AbstractContextProvider.java:133) at oracle.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport$3.method(DefaultMutableAppServerContext.java:384) at oracle.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport$MethodCall.invoke(DefaultMutableAppServerContext.java:421) at oracle.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport.listBindings(DefaultMutableAppServerContext.java:381) at oracle.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport.access$500(DefaultMutableAppServerContext.java:314) at oracle.rc.asadapter.context.spi.DefaultMutableAppServerContext.localListBindings(DefaultMutableAppServerContext.java:207) at oracle.rc.asadapter.context.spi.AbstractEventDirContext.listBindings(AbstractEventDirContext.java:185) at oracle.adf.rc.spi.jndi.AbstractDirContext.listBindings(AbstractDirContext.java:214) at oracle.rc.asadapter.context.spi.DefaultAppServerManageableContext.getManageables(DefaultAppServerManageableContext.java:58) at oracle.jdeveloper.asnav.nodes.DefaultManageableFolder.loadChildren(DefaultManageableFolder.java:327)
    No Bugmate found.