cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

BackGroundMethodServer queues overloaded during mass changes

SOLVED
Highlighted
Level 7

BackGroundMethodServer queues overloaded during mass changes

Hi,

 

We have experienced the Background Method Server queues being very busy due to mass changes. This causes smaller background jobs to be placed at the end of the queue and users have to wait several hours before their job is processed.

 

Example.
- Change initiated on a part that is used in many bom’s
- All kinds of activities are send to the queue. e.g.
  -  Promotion / Set state jobs

  -  ESI sendings
  -  Etc.
- All of this is processed in the WFPropagationQueue, which obviously takes some time to process.
- But, when other user then does some simple stuff like promote, set state, start NC, etc, there job will be placed at the end of the queue.
- This causes frustration among our users, and they think, the system did not catch their first attempt. Eventually they perform the same action multiple time and complain about a slow system.

 

So, now I would like to find a solution, where these long running jobs can mind their own business, while other jobs can be processed in parallel, if possible.


I have read some articles in the knowledge base about setting up multiple background Method Servers and how they can be configured to take care of different queues, but I am not sure how to get to a result that will solve our issue.

 

Anybody with experience or good ideas?

 

/Kim

1 ACCEPTED SOLUTION

Accepted Solutions

Re: BackGroundMethodServer queues overloaded during mass changes

What I understood from your requirement is - you are looking to segregate queue processing of Change Management workflows from rest other workflows. If it is true, then I believe dedicated queue functionality can solve the purpose. Dedicated queue can be created for a specific workflow template which are used heavily in the system and their processing can be separated from other regular workflow processes. Couple of properties, a flag in the workflow template and extensive testing is required to enable this on production.

 

You can check more details in guide(Section : Dedicated Queues):

 

http://support.ptc.com/WCMS/files/156798/en/WCSpecializedAdminGuide.pdf

2 REPLIES

Re: BackGroundMethodServer queues overloaded during mass changes

What I understood from your requirement is - you are looking to segregate queue processing of Change Management workflows from rest other workflows. If it is true, then I believe dedicated queue functionality can solve the purpose. Dedicated queue can be created for a specific workflow template which are used heavily in the system and their processing can be separated from other regular workflow processes. Couple of properties, a flag in the workflow template and extensive testing is required to enable this on production.

 

You can check more details in guide(Section : Dedicated Queues):

 

http://support.ptc.com/WCMS/files/156798/en/WCSpecializedAdminGuide.pdf

Re: BackGroundMethodServer queues overloaded during mass changes

Thanks AbhijeetMule. So far this seems to do the job Smiley Happy