java.lang.NumberFormatException

If you like a tip written by other Samebug users, mark is as helpful! Marks help our algorithm provide you better solutions and also help other users.
tip

Java does not handle IPv6 nameservers before 1.8.0_60. Upgrade to the latest JVM.


rprp
tip

This is a bug in Wise, updating to v4.10 seems to solve the problem.

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

  • dscc add agent problem
    via by 2899738,
  • Kafka Timeline
    via by Unknown author,
  • Crash by clicking Kendzi 3D View
    via GitHub by Maskulinum
    ,
    • java.lang.NumberFormatException: For input string: "\sun\dsee7\var\dcc\agent:399 8" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at com.sun.jndi.toolkit.url.Uri.parse(Uri.java:214) at com.sun.jndi.toolkit.url.Uri.init(Uri.java:120) at com.sun.jndi.ldap.LdapURL.<init>(LdapURL.java:67) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:146) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134) at com.sun.directory.common.ssl.LdapContextUtils$3.run(LdapContextUtils.java:252) at java.lang.Thread.run(Thread.java:662)

    Users with the same issue

    HandemelindoHandemelindo
    24 times, last one,
    derproggerderprogger
    2 times, last one,
    DavidDavid
    2 times, last one,
    rocdayrocday
    2 times, last one,
    MattyMatty
    4 times, last one,
    190 more bugmates