This is a bug that happens in Slide in versions 4.2.0 and before. Update to 4.2.2 or further to fix it.

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • Catch a root cause exception under a Java IO Exception
    via by Prasanna krishnan,
  • Catch a root cause exception under a Java IO Exception
    via by Prasanna krishnan,
  • Not able to configure IDM in RHEL
    via by 2844987,
  • Problems with Agent.
    via by 743092,
  • OLT-Running Load Testing Scripts using agents
    via by user13062020,
  • [OTM] - Run Test Scripts using agent
    via by 2944602,
  • rmi - HTTP tunneling
    via by 3004,
    • stpcy05] 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 Caused by: stpcy05 at Method) at$1.lookupAllHostAddr( at at at at at weblogic.rjvm.RJVMFinder.getDnsEntries( at weblogic.rjvm.RJVMFinder.findOrCreateInternal( at weblogic.rjvm.RJVMFinder.findOrCreate( at weblogic.rjvm.ServerURL.findOrCreateRJVM( at weblogic.jndi.WLInitialContextFactoryDelegate$ at at at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( ... 11 more

    Users with the same issue

    18 times, last one,
    Hiren AmaliyarHiren Amaliyar
    27 times, last one,
    Михайло ТітовМихайло Тітов
    420 times, last one,
    1 times, last one,
    Andreas HäberAndreas Häber
    1 times, last one,
    130 more bugmates