java.lang.NumberFormatException

For input string: "L"

Samebug tips2

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


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

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web5370

  • via Stack Overflow by HahnSolo
    , 3 months ago
    For input string: "l"
  • via Google Groups by Christine, 2 weeks ago
    For input string: "L"
  • For input string: "L"
  • Stack trace

    • java.lang.NumberFormatException: For input string: "L" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.valueOf(Integer.java:582) at org.springframework.scheduling.support.CronSequenceGenerator.getRange(CronSequenceGenerator.java:324) at org.springframework.scheduling.support.CronSequenceGenerator.setNumberHits(CronSequenceGenerator.java:297) at org.springframework.scheduling.support.CronSequenceGenerator.setDays(CronSequenceGenerator.java:275) at org.springframework.scheduling.support.CronSequenceGenerator.setDaysOfMonth(CronSequenceGenerator.java:266) at org.springframework.scheduling.support.CronSequenceGenerator.parse(CronSequenceGenerator.java:239) at org.springframework.scheduling.support.CronSequenceGenerator.<init>(CronSequenceGenerator.java:81) at org.springframework.scheduling.support.CronTrigger.<init>(CronTrigger.java:54) at org.springframework.scheduling.support.CronTrigger.<init>(CronTrigger.java:44) at com.hcdc.coedp.datantar.scheduler.SchedulerUtil.start(SchedulerUtil.java:75) at com.hcdc.coedp.datantar.scheduler.SchedulerUtil.changeTrigger(SchedulerUtil.java:106) at com.hcdc.coedp.datantar.scheduler.SchedulingService.scheduleTransfer(SchedulingService.java:70) at com.hcdc.coedp.datantar.scheduler.Scheduler.schedule(Scheduler.java:107) at main.Main.main(Main.java:47)

    Write tip

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

    Users with the same issue

    4 times, 1 month ago
    4 times, 2 months ago
    16 times, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    208 more bugmates