java.lang.IllegalArgumentException

Cannot convert Mon Feb 09 00:00:00 CET 2015 of typejava.util.Date

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web2

  • via Unknown by manolo perez,
  • via Unknown by manolo perez,
  • Stack trace

    • java.lang.IllegalArgumentException: Cannot convert Mon Feb 09 00:00:00 CET 2015 of typejava.util.Date at ch.qos.logback.core.rolling.helper.IntegerTokenConverter.convert(IntegerTokenConverter.java:40) at ch.qos.logback.core.rolling.helper.FileNamePattern.convert(FileNamePattern.java:137) at ch.qos.logback.core.rolling.helper.TimeBasedArchiveRemover.cleanByPeriodOffset(TimeBasedArchiveRemover.java:28) at ch.qos.logback.core.rolling.helper.DefaultArchiveRemover.clean(DefaultArchiveRemover.java:71) at ch.qos.logback.core.rolling.TimeBasedRollingPolicy.start(TimeBasedRollingPolicy.java:100) at org.jga.camel.AppDispatcher$1.buildAppender(AppDispatcher.java:134) at ch.qos.logback.core.sift.AppenderTracker.buildComponent(AppenderTracker.java:57) at ch.qos.logback.core.sift.AppenderTracker.buildComponent(AppenderTracker.java:32) at ch.qos.logback.core.spi.AbstractComponentTracker.getOrCreate(AbstractComponentTracker.java:124) at ch.qos.logback.core.sift.SiftingAppenderBase.append(SiftingAppenderBase.java:105) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:85) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:273) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:260) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:442) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:396) at ch.qos.logback.classic.Logger.info(Logger.java:600) at org.jga.camel.connectors.Conn1.doWork(Conn1.java:13) at org.jga.camel.AppDispatcher.main(AppDispatcher.java:173)

    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

    We couldn't find other users who have seen this exception.