org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: org.apache.wicket.WicketRuntimeException: There is no application attached to current thread DefaultQuartzScheduler_Worker-1]

Stack Overflow | Kurt Clauss | 6 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Wicket serialization issue with WebApplication

    Stack Overflow | 6 months ago | Kurt Clauss
    org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: org.apache.wicket.WicketRuntimeException: There is no application attached to current thread DefaultQuartzScheduler_Worker-1]

    Root Cause Analysis

    1. org.apache.wicket.WicketRuntimeException

      There is no application attached to current thread DefaultQuartzScheduler_Worker-1

      at org.apache.wicket.Application.get()
    2. Wicket Core
      WebApplication.get
      1. org.apache.wicket.Application.get(Application.java:236)
      2. org.apache.wicket.protocol.http.WebApplication.get(WebApplication.java:160)
      2 frames
    3. eb.wicket.behaviors
      LogWebSocketBehavior$1.publish
      1. eb.wicket.behaviors.LogWebSocketBehavior.sendToAllConnectedClients(LogWebSocketBehavior.java:77)
      2. eb.wicket.behaviors.LogWebSocketBehavior.access$100(LogWebSocketBehavior.java:29)
      3. eb.wicket.behaviors.LogWebSocketBehavior$1.publish(LogWebSocketBehavior.java:70)
      3 frames