Browse Prior Art Database

System to store thread and machine states in a printer while processing a "slow" or "hung" page image

IP.com Disclosure Number: IPCOM000244546D
Publication Date: 2015-Dec-21
Document File: 1 page(s) / 37K

Publishing Venue

The IP.com Prior Art Database

Abstract

In a printing system, a thread monitors every page being processed and, if a page completes, collects the time taken for the process and stores it in an array. The array values will be averaged when the array will receive a new page value time. If any page exceeds the average time by configurable threshold time value, immediately the thread or process will get all the status and information will pack it and store somewhere in the storage. The system can then present the information to the user. Benefits include the ability to identify pages in a print job that are slow to process relative to the pages already being processed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 64% of the total text.

Page 01 of 1

System to store thread and machine states in a printer while processing a "slow" or "hung" page image

In digital printing, especially of large documents or jobs, a process or job can be "hung" (delayed) in a file which contains multiple pages, and the customer will not get any information about where and why and which number of page hung while processing.

There is proposed a thread, within or outside the rasterizing or printing process, that monitors every page processing and if a page completes this method will collect the time taken for the process and stored it in a array kind of form. The array values will be averaged when the array receives a new page value time. If any page exceeds the average time by configurable threshold time value, immediately the thread or process will get all the status and information will pack it and store somewhere in the storage.

In a multipage processing system, if a file is hung in a page, this method will get the information and the other status of that process to help the customer to identify the problematic page and the status of the process, like call stacks and other information.

If a process P1 is having many threads and it will be monitor by a Timer thread T1 within the process or a Timer process from outside the process P2. T1 or P2 will get the information of the time taken for the page to complete on a per page basis. T1 will store that value in an array type of form and will always average the value of the array type...