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.

  • JMS SSL - hardware loadbalancer
    via by 666705,
  • Problems with remote ejb on weblogic
    via by Fausto Calderazzo,
  • javax. naming. CommunicationException
    via by Parameswaran Thangavel,
  • db:: 3.80::TLS Handshake fails on Mac OS X fk
    via by Unknown author,
  • Error retrieving resource
    via by 666705,
    • Bootstrap to:' over: 'https' got an error or timed out] at weblogic.jndi.internal.ExceptionTranslator.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( at weblogic.jndi.WLInitialContextFactory.getInitialContext( at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at TestAllManagedServers.main( Caused by: Bootstrap to:' over: 'https' got an error or timed out at weblogic.rjvm.RJVMFinder.findOrCreate( at weblogic.rjvm.ServerURL.findOrCreateRJVM( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( ... 7 more

    Users with the same issue

    Unknown visitor1 times, last one,