0 Replies Latest reply on Sep 25, 2013 10:00 AM by Oriol R.

    Unresolved Remote JNDI Link prevents Weblogic from starting?

    Oriol R.

      Hi, we are facing an issue regarding one WebLogic server not serving requests due to an unresolved remote JNDI name not found on a second WLS. Is it possible that checking the availability of all JNDI names -local and remote- is critical for WLS startup?


      We can see that the WLS starts alright, but all requests get 500 Internal Server Error right away until the remote JNDI name exists again.


      Could you please shed some light on this?

      Thanks in advance!