I currently have 16 active jobs which I use the Data Services Management Console to schedule the ETL jobs.
I have 12 scheduled to used my production job server. If I attempt to schedule the 13th using the production job server I get the error "Error while adding a job to scheduler ". If I change the job server in that identical schedule to the development job server the job successfully schedules.
Similar if I deactivate one of the 12 scheduled jobs using the prod job server and then attempt to schedule another job against the prod job server it is successful.
Anyone aware of the number of jobs which can be scheduled to a job server?
Environment:
OS: Windows 2008
DB: SQL Server 2008
DS: 3.2
I don’t think there is a limit on number of jobs you can schedule on a job server
is there more details in the error message ?
check if there is anything logged in the %LINK_DIR%\log\web_admin.log.0 file
also, right click on the page when you get this error ,and see if there is a java stack trace, if yes, then post the stack trace
<!--
com.acta.util.ActaException: Error while adding a job to scheduler
at com.acta.webapp.admin.report.AwScheduleBatchJobPage.scheduleit(Unknown Source)
at com.acta.webapp.admin.report.AwScheduleBatchJobPage.newAction(Unknown Source)
at com.acta.webapp.mdreport.common.DIView.doAction(Unknown Source)
at com.acta.webapp.mdreport.common.DIView.PrintReport(Unknown Source)
at com.acta.webapp.mdreport.common.DIViewController.PrintReport(Unknown Source)
at com.acta.webapp.mdreport.reportframework.JCActaGenericSection.PrintReport(Unknown Source)
at com.acta.webapp.mdreport.common.DIFrame.PrintReport(Unknown Source)
at com.acta.webapp.mdreport.common.DIMainFrame.PrintReport(Unknown Source)
at com.acta.webapp.mdreport.common.DIBaseReport.PrintMainFrame(Unknown Source)
at com.acta.webapp.mdreport.common.DIBaseReport.PrintReportImpl(Unknown Source)
at com.acta.webapp.mdreport.common.DIBaseReport.PrintReport(Unknown Source)
at com.acta.webapp.admin.servlet.AwBatchJobScheduleServlet.doPostSafe(Unknown Source)
at com.acta.webapp.mdreport.reportframework.JSActaHttpServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.acta.webapp.mdreport.servlet.JSFilter.doFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.acta.webapp.mdreport.servlet.EscapeFilter.doFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
---
**chuckdiegoo** _(BOB member since 2009-10-12)_
from the stack trace, the problem is happening in the begining of the saving of schedule, may be some input is getting initialzed incorrectly, what are the schedule options that you are passing ? like once a day, multiple times a day etc
does this job has global variables, or substitution params ? try creating one more schedule for the job that was scheduled successfully
if the problem is happening while scheduling on a particular job server then check the server_event_.log file of that job server if any errors are logged ?
I reproduced the error again this morning, here is the entry in the log file:
(12.2) 09-30-10 09:08:46 (8516:9540) JobServer: AddSchedule:fails : Error while adding a job to scheduler (BODI-850112)
Some additional history:
1] I have tried to remove all scheduled jobs and recreate the job service, however once I get to the magical number the error continues.
2] I have tried scheduling job with a different job server on the same server and the error continues. This proves that it is not a particular job server causing the problem.
Could it be that there is a ghost job on the windows server which is block this newly created job?
looks like there is a problem adding a schedule from windows scheduler, the jobServer is not able to create the schedule in windows scheduler
check the system event log? do you see any errors for the windows scheduler or jobserver application?
since you are able to reproduce the issue, try following
export the execution command of that batch job to the Jobserver which having this issue
go to windows schedule task and add a new task, point it to execute the batch job execution script, set the same schedule information that you are setting in Management Console