Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,

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

  2. ,
    Expert tip

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

Solutions on the web

via Oracle Community by 2899738, 1 year ago
For input string: "\sun\dsee7\var\dcc\agent:399 8"
via Oracle Community by 843793, 1 year ago
via Stack Overflow by Kyle
, 11 months ago
via Stack Overflow by Warren
, 2 years ago
via GitHub by Nandutu
, 1 year ago
For input string: ""
via GitHub by demaniak
, 10 months ago
For input string: "8088,80"
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.(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.(InitialLdapContext.java:134)	at com.sun.directory.common.ssl.LdapContextUtils$3.run(LdapContextUtils.java:252)	at java.lang.Thread.run(Thread.java:662)