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.

  • JNDI lookup fails JDeveloper-Weblogic
    via by user7245827,
  • WLST connects rarely
    via by togotutor,
  • Can't do t3s from 12.1 to 10.3
    via by John Gregg,
  • SSL JMX Java client
    via by user13676935,
  • db:: 3.87::Received fatal alert: handshake_failure x9
    via by Unknown author,
  • 11g: ALSB Statistics Manager and t3s
    via by user10939158,
    • Empty server reply; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( at weblogic.jndi.Environment.getContext( at weblogic.jndi.Environment.getContext( at weblogic.jndi.WLInitialContextFactory.getInitialContext( at javax.naming.spi.NamingManager.getInitialContext( at javax.naming.InitialContext.getDefaultInitCtx( at javax.naming.InitialContext.init( at javax.naming.InitialContext.<init>( at HelloWorldClient.main(
    No Bugmate found.