Sven Vanleke Posted September 7, 2012 Share Posted September 7, 2012 Hi,We recently performed the upgrade to get our server from v4.5.0 to v4.7.0.Everything went wel without any visible error and the online interface came up nicely as expected.Even all report jobs were there as before (online check + "http://{host}:{port}//jasperserver/rest_v2/jobs?")Unfortunaltely all schedules for these jobs have a state "unknown" (cf. attachment)As we execute them manually (run) everything is OK, but the schedule, which was set in v4.5.0, has that state "unknown"Could anyone point me in the right direction in order to have these schedules active again or to be able to debug/log them?The system involved: Windows Server 2008 R2, Tomcat 7.0 and PostgreSQL 9.0.4Kind regards,Sven Vanleke Link to comment Share on other sites More sharing options...
Sven Vanleke Posted September 10, 2012 Author Share Posted September 10, 2012 Anyone to guide me to the proper info? Tnx! Link to comment Share on other sites More sharing options...
oesina Posted September 10, 2012 Share Posted September 10, 2012 Hi Sven, could you please check your Tomcat log files? Usually you will get some more information about report & job executions. Hopefully you will get some hints from the logs,Regards,Olga Link to comment Share on other sites More sharing options...
Sven Vanleke Posted September 10, 2012 Author Share Posted September 10, 2012 Thank you Olga for your feedback!I added com.jaspersoft.jasperserver.api.engine.scheduling.quartz in de Log Setting with "Debug" as an option. When I checked the logfiles (tomcat7-stdout.log & Jasperserver.log)I noticed the following errors:2012-09-10 10:50:06,784 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 158562012-09-10 10:50:06,790 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 158562012-09-10 10:50:06,796 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 49642012-09-10 10:50:06,801 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 49642012-09-10 10:50:06,807 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 157972012-09-10 10:50:06,811 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 157972012-09-10 10:50:06,816 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 159152012-09-10 10:50:06,819 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15915Apprently the jobs are still there with definitions, parameters en schedule but somehow the link between them is corrupt.I still hope that recreating the definitions again is not the only solution since the upgrade has gone smoothly without errors and hope to use the same upgrade-procedure in the future.Does the error ring a bell for someone so that I can reinstate my existing report jobs?Regards.Post Edited by svenvanleke at 10/09/2012 11:05 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now