Company Products Partners Help Desk News Success Stories Contact US Home Page
Support Center » Knowledgebase » Job status configuration
 Login [Lost Password] 
Email:
Password:
Remember Me:
 
 Search
 Article Options
 Job status configuration
Solution

The Job Status Service has 2 mechanisms: The Read mechanism and the Run mechanism.

The Read mechanism is responsible of reading real-time job status information while the Run mechanism is responsible for running ready jobs, clearing idle jobs, canceling canceled jobs and any job status changes and manipulations. The Run mechanism depends on the Read mechanism, since it uses the real time information that the Read mechanism retrieves.

 

JOBSTATUS_READ_ALL_REFRESH_MILLISEC

 

Value range: 200 – 120000

Default: 600 (0.6 seconds)

 

JOBSTATUS_RUN_JOBS_REFRESH_MILLISEC

 

Value range: 600 – 360000 (Must be at least 3x than the Read all refresh time)

Default: 5000 (5 seconds)

 

 

When the Read or Run refresh values are too low compared to the number of computes in the Print Lab, the following side effects may appear:

 

  • Jobs are printed twice, once on each station.
  • Jobs may “flicker” between Ready state and Running state.
  • Cancel Job may need to be pressed multiple times for job to be canceled.
  • Orders may be locked forever and may need to be manually released.
  • CPU usage may reach 100%, resulting in performance issues and errors.

 

The following table displays the recommended settings for proper Read / Run settings values:

 

 

Number of computers

Read

Run

1 – 2

600

5000

2 – 5

1500

10000

5 – 10

3000

20000

10 – X

5000

30000

 

 



 

 



Article Details
Article ID: 92
Created On: 10 Sep 2009 12:57 PM

 This answer was helpful  This answer was not helpful

 Back
Home | Register | Submit a Ticket | Knowledgebase | Troubleshooter | News
Language:

Help Desk Software by Kayako SupportSuite v3.30.02