search

annadalok / myschedule

Automatically exported from code.google.com/p/myschedule
0 stars 1 forks source link

NPE when viewing trigger details page. #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Sometimes a NPE error page will resulted when viewing Trigger detail page. 
{{{
java.lang.NullPointerException
    at myschedule.quartz.extra.SchedulerTemplate.getNextFireTimes(SchedulerTemplate.java:648)
    at myschedule.web.servlet.app.handler.JobHandlers$12.handleViewData(JobHandlers.java:278)
    at myschedule.web.servlet.UrlRequestActionHandler.handleAction(UrlRequestActionHandler.java:49)
    at myschedule.web.servlet.ActionHandlerServlet.process(ActionHandlerServlet.java:104)
    at myschedule.web.servlet.AbstractControllerServlet.doGet(AbstractControllerServlet.java:56)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:619)
}}}

To reproduce:
  1. Start MySchedule with a in memory scheduler config already created.
  1. Goto Scripting page and schedule a job.
  1. Goto Job listing page, and click on the Trigger link.

Workaround:
  1. Goto Dashboard view, click on the scheduler name link.
  1. Goto Job listing page, and click on the Trigger link.

I think there the session for the current scheduler is not set correctly.

Original issue reported on code.google.com by saltnlight5 on 15 Nov 2011 at 11:45

GoogleCodeExporter commented 9 years ago 
Hum ... this is not re-producable after the trigger-detail page is fixed.

Original comment by saltnlight5 on 16 Nov 2011 at 1:08

GoogleCodeExporter commented 9 years ago 
I think this issue is related to Issue53, which is fixed now.

Original comment by saltnlight5 on 17 Nov 2011 at 2:14