commonScheduleQueue

The commonScheduleQueue is used for a variety of low-volume queue entries. These low-volume entries require limited resources and are often run only once or infrequently. Combining these queue entries into the commonScheduleQueue frees system resources to focus on high-volume queues. The following list describes each commonScheduleQueue entry type:

• LicenseGroupMembershipLinks queue entries are scheduled to synchronize the participants in the View and Print Only license group with the View and Print Only Licenses table.

By default, a queue entry of this type is scheduled to run every midnight (0:00 AM GMT). The run time of the entry can be configured using the wt.org.CreateLicenseGroupMembershipLinkWeeklyQueueTime and the wt.org.CreateLicenseGroupMembershipLinkDayOfWeek properties.

Depending on when changes to group membership occur in relation to the scheduled run time of the entry, it can take up to one day for the View and Print Only Licenses table to reflect the membership change.

• StandardRecentlyVisitedService queue entries are created to remove the oldest items from all recently visited lists when the total number of list items exceeds the value specified for the wt.recent.objectStackSize property located in the wt.properties file. The default value for this property is 100.

A queue entry of this type is scheduled to run at midnight (0:00 AM GMT) the first time the StandardRecentlyVisitedService is started. Every time the queue task runs, it re-schedules itself to run again at midnight (0:00 AM GMT) on the following day.

• StandardPurgeService queue entries are created to cleanup canceled purge jobs. Queue entries of this type are only created when the wt.queue.executeQueues property is set to true. By default this property is set to true.

A queue entry of this type is scheduled to run every midnight (0:00 AM GMT). When the queue task runs it deletes cancelled purge jobs older than a day and which also have a status of Awaiting preview.

• StandardCollectionService queue entries are created to disable queries with invalid criterion. This queue entry is only created when the both the wt.queue.executeQueues and wt.dataops.objectcol.cleanUpEnabled properties are set to true. By default, both of these properties are set to true.

A queue entry of this type is scheduled to run at midnight (0:00 AM GMT) once every seven days. It disables queries with invalid criterion. For example, it would disable a query that has a folder reference that has been deleted. Disabled queries are not visible to users viewing the Queue Management user interface.

• MarkForDeleteQueue entries are used by Windchill ProjectLink to implement the marking of projects and their contents as deleted. When a project is marked as deleted (using the Delete action), it no longer appears in any project member's My Projects list. The marking process is done in the background to improve user response time.

The system automatically sends a notification to the project managers group if the deletion of a project fails. The notification includes the exception message that caused the failure. The project manager should investigate the reason for the failure, correct it, and reattempt a project deletion by selecting the project Delete action again.

You should periodically check the commonScheduleQueue for failed MarkForDeleteQueue entries. If an entry has a failed status, the only action needed is to remove it from the queue.

• PagingScheduleQueue entries are used by Local Search to clean up temporary results that are stored in the database. The results are associated with search requests of each user. There is only one entry regardless of the number of users executing Local Search.

A failed entry means that the temporary results will not be cleaned up and may impact performance if the data grows too large. If the commonScheduleQueue queue is able to successfully create a new entry, then a subsequent execution will clean up all data (including the data from previous attempts).

You should check the commonScheduleQueue queue each day for failed PagingScheduleQueue entries to ensure that it the temporary results stored in the database are being cleaned up. Intermittent failures are not critical because the successful processing will clean up all data from previous failures. However, all failures should be investigated and reported through PTC Technical Support.

Effectivity audit objects are created to track the creation and factual deletion of effectivity objects. A factual deletion means that an effectivity record is marked as deleted, but is retained as historical information. When effectivity objects are actually deleted, audit objects can become unreferenced, thus, having no further purpose. Checking for corresponding audit objects each time that an effectivity object is actually deleted is time consuming; therefore, this non-urgent clean up is done on a scheduled basis (by default, once a day). To change the schedule for the cleanup, change the interval time set in the wt.eff.EffChangeAudit.purgeInterval property, which is located in the wt.properties file. Express the interval time in minutes; the default value is 1440 minutes (one day).

Failed PurgeOrphanedEffAuditsQueue entries mean an attempt to query for and delete the audit items has failed. Checking for failed PurgeOrphanedEffAuditsQueue entries is not needed on a regular basis. Each queue entry has identical functionality; therefore, if failed entries are noticed, they can be deleted (since they will be replaced by future ones). If the problem occurs chronically, check the system configuration and consider filing a problem report with PTC Technical Support. Also, since the Effectivity service is programmed to create this queue on startup (if it does not exist), a problematic instance of the queue can simply be deleted, along with all of its entries (regardless of their status).

• StatisticsScheduleQueue entries are used by the subtype/attribute query service to gather statistics related to global attributes (previously known as IBAs). These statistics are used when optimizing queries.

A failed queue entry implies that statistics were not collected. If statistical data is not up-to-date, then the soft type/attribute query performance may not be optimized.

The frequency for gathering the statistics is controlled by the com.ptc.core.query.optimize.statisticsBasedRankGenerator.queueInvokeTime property setting. The default is once a day. See properties.html for details.