Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Chunzhi Hong (Chunzhi_Hong)
PEGA
Principal System Architect
Pegasystems Inc.
JP
Chunzhi_Hong Member since 2013 143 posts
PEGA
Posted: May 24, 2019
Last activity: Dec 26, 2019
Posted: 24 May 2019 3:44 EDT
Last activity: 26 Dec 2019 12:01 EST
Closed
Solved

Does DSS setting "prconfig/services/maxrequestorchildren/default" really work?

In Pega Platform v7.4, it seems that "services/maxrequestorchildren" does NOT impose any restriction on how many childe requestors being created.

Below is my test result. 20 distinct requestors are created despite max requestor for children is only 5.

PegaRULES.log

2019-05-24 03:10:16,216 [ttp-nio-8080-exec-10] [ STANDARD] [ ] [ PoC74:01.01.01] (ivity.OWD7K2_PoC74_Work.Action) INFO lab5190| Proprietary information hidden|SOAP|PoC74Work|Services|ServiceActivity|A887XJFVHII8V20NSDD9AJZNE6BBXWBK7 - ************ Begin Service ****************

2019-05-24 03:10:16,245 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 203 For Pega RequestorID=BO6KZCXDWAVP16VYWZMN80U2MKVQT8NU9 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,246 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 202 For Pega RequestorID=B666JEPHG4PRZS86EX3C9ZALSD8ZMZDCZ maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,246 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 121 For Pega RequestorID=BZNMPQABXRC2X0TKPF4EO9UFOKS8FMBES maxRequestorChildren=5 agentThreadPoolSize=null

Show More

In Pega Platform v7.4, it seems that "services/maxrequestorchildren" does NOT impose any restriction on how many childe requestors being created.

Below is my test result. 20 distinct requestors are created despite max requestor for children is only 5.

PegaRULES.log

2019-05-24 03:10:16,216 [ttp-nio-8080-exec-10] [ STANDARD] [ ] [ PoC74:01.01.01] (ivity.OWD7K2_PoC74_Work.Action) INFO lab5190| Proprietary information hidden|SOAP|PoC74Work|Services|ServiceActivity|A887XJFVHII8V20NSDD9AJZNE6BBXWBK7 - ************ Begin Service ****************

2019-05-24 03:10:16,245 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 203 For Pega RequestorID=BO6KZCXDWAVP16VYWZMN80U2MKVQT8NU9 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,246 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 202 For Pega RequestorID=B666JEPHG4PRZS86EX3C9ZALSD8ZMZDCZ maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,246 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 121 For Pega RequestorID=BZNMPQABXRC2X0TKPF4EO9UFOKS8FMBES maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,247 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 123 For Pega RequestorID=B335JBFNMF7CFJOAEJ5WD1OUSEONL5D43 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,248 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 120 For Pega RequestorID=BXAL0X8H35630LO5VKESXE7YZ4ACK2W28 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,351 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 123 For Pega RequestorID=B0GZRQRCVFI27AZZBFGOYHUKDMU95RAYB maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,351 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 120 For Pega RequestorID=BCFSOG19MT6F1ORNY8UG5A6DGSWL6CMAF maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,352 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 202 For Pega RequestorID=BIOO65KTY3F2B6W6RKGMTS6QTJJMW0WW2 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,353 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 203 For Pega RequestorID=BZHQ0KM7WPLOKR85DR0M2GA1P54I82WVA maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,353 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 121 For Pega RequestorID=BVPM2EIQY7PF8TRNOE5WYMOOJ8J55GVEK maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,455 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 120 For Pega RequestorID=BNKOKNDBWDUZ4UMS7YU7CYNAVN8ASUFBD maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,455 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 123 For Pega RequestorID=B1MSAWNSISWLIOAYY05BK582MPPGLXGI8 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,456 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 202 For Pega RequestorID=BU6S1FT3BDNO4AA0C326IXJTOL5LJN510 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,457 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 121 For Pega RequestorID=BLZVSHR9Z1TY0E1R07QT4QAA8IAHMPI0O maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,459 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 203 For Pega RequestorID=B8M2SQ6K911U80QEUNI39OA40FE57PUYK maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,559 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 120 For Pega RequestorID=BO19C703KB16KAKP14FM30YJ7OZLFISH0 maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,560 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 202 For Pega RequestorID=BXZM17AO359I45G5P5L9S4NW5POU58VJF maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,561 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 121 For Pega RequestorID=BNYKHLOS28VQ47RW4YIOCT8LWN0Z39L1O maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,561 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 123 For Pega RequestorID=B25R5X8MH59T7LUD1SJYSRXBSZ49MZZAM maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:16,562 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PoC74:01.01.01] (eadID.OWD7K2_PoC74_Work.Action) INFO - JVM Thread ID- 203 For Pega RequestorID=BUIJBUOK6NAKVCT4S9KTTIQM9BXEEFDBR maxRequestorChildren=5 agentThreadPoolSize=null

2019-05-24 03:10:25,242 [ttp-nio-8080-exec-10] [ STANDARD] [ ] [ PoC74:01.01.01] (ivity.OWD7K2_PoC74_Work.Action) INFO lab5190| Proprietary information hidden|SOAP|PoC74Work|Services|ServiceActivity|A887XJFVHII8V20NSDD9AJZNE6BBXWBK7 - ************ End Service ****************


Show Less
To see attachments, please log in.
Low-Code App Development
System Administration
Support Case Created

Accepted Solution

Posted: 4 years ago
Posted: 26 Dec 2019 12:01 EST
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

Upon reviewing the associated SR, the resolution was shared as the following:
 

There are two ways to create batch requestors to implement asyncprocessing. One is to create a new batch requestor as a detached task and the other is to create a child requestor so that the parent requestor can wait on the child requestor to complete.

The API, queueBatchActivity has overloaded APIs to support these behaviors. There is a single thread pool which is used by agents, detached batch requestors and child requestors and the size of this can be configured via “agent/threadpoolsize”.

 

Show More

Upon reviewing the associated SR, the resolution was shared as the following:
 

There are two ways to create batch requestors to implement asyncprocessing. One is to create a new batch requestor as a detached task and the other is to create a child requestor so that the parent requestor can wait on the child requestor to complete.

The API, queueBatchActivity has overloaded APIs to support these behaviors. There is a single thread pool which is used by agents, detached batch requestors and child requestors and the size of this can be configured via “agent/threadpoolsize”.

 

Creation of child requestors

  1. “Run in parallel” option in the Connect- * methods, Connect-CMIS, Connect-EJB, Connect-JCA, Connect-JMS, Connect-Java, Connect-MQ,Connect-SAP, Connect-SAPJCo, Connect-SOAP
  2. “Run in parallel” option on all the four RDB-* methods
  3. Public API for queueBatchActivity which allows creation of child requestors

Creation of detached batch requestors

  1. Queue method
  2. Parallel option in rule-declare-trigger

Show Less
To see attachments, please log in.
Posted: 5 years ago
Posted: 24 May 2019 6:45 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

I am not sure your test is valid. The setting is still there in the latest code, it controls the maximum child requestor for a given parent requestor. Normally use queueBatchActivity to test.

To see attachments, please log in.
Posted: 5 years ago
Posted: 24 May 2019 7:06 EDT
Chunzhi Hong (Chunzhi_Hong)
PEGA
Principal System Architect
Pegasystems Inc.
JP

Hi Kevin,

I used Queue method in my service activity. I didn’t use queueBatchActivity engine API. 

Chunzhi

To see attachments, please log in.
  • Matt Healy Fernando Diaz De La Fuente Nagarjuna Reddy Mandati Daniel Mercurio

Accepted Solution

Posted: 4 years ago
Posted: 26 Dec 2019 12:01 EST
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

Upon reviewing the associated SR, the resolution was shared as the following:
 

There are two ways to create batch requestors to implement asyncprocessing. One is to create a new batch requestor as a detached task and the other is to create a child requestor so that the parent requestor can wait on the child requestor to complete.

The API, queueBatchActivity has overloaded APIs to support these behaviors. There is a single thread pool which is used by agents, detached batch requestors and child requestors and the size of this can be configured via “agent/threadpoolsize”.

 

Show More

Upon reviewing the associated SR, the resolution was shared as the following:
 

There are two ways to create batch requestors to implement asyncprocessing. One is to create a new batch requestor as a detached task and the other is to create a child requestor so that the parent requestor can wait on the child requestor to complete.

The API, queueBatchActivity has overloaded APIs to support these behaviors. There is a single thread pool which is used by agents, detached batch requestors and child requestors and the size of this can be configured via “agent/threadpoolsize”.

 

Creation of child requestors

  1. “Run in parallel” option in the Connect- * methods, Connect-CMIS, Connect-EJB, Connect-JCA, Connect-JMS, Connect-Java, Connect-MQ,Connect-SAP, Connect-SAPJCo, Connect-SOAP
  2. “Run in parallel” option on all the four RDB-* methods
  3. Public API for queueBatchActivity which allows creation of child requestors

Creation of detached batch requestors

  1. Queue method
  2. Parallel option in rule-declare-trigger

Show Less
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice