PRPCWorkManager Threadcount very high
Hi there,
We're noticing a higher than normal thread count (100+) and have 20 as a the maximum specified for the PRPCWorkManager. Is this just a reporting issue where the count is not displaying correctly or could this be a different issue?
Hi there,
We're noticing a higher than normal thread count (100+) and have 20 as a the maximum specified for the PRPCWorkManager. Is this just a reporting issue where the count is not displaying correctly or could this be a different issue?
[4/3/17 6:23:58:413 MST] 0000001a SystemOut O 2017-04-03 06:23:58,413 [ WebContainer : 3] [TABTHREAD4] [ ] [GPSAPOINTER:01.01.01] (s.generated.gpsa_xxxxgpsautils) INFO xxxxxxxxx| Proprietary information hidden 0060441 - ### EndLog Call Variables Page after mapping from Dialer Page#####
[4/3/17 6:30:22:894 MST] 0000001a SystemOut O 2017-04-03 06:30:22,894 [RPCWorkManager : 117] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Mon Apr 03 06:30:22 MST 2017 Total memory: 2,147,483,648 Free memory: 733,775,288 Requestor Count: 21 Shared Pages memory usage: 0%
[4/3/17 6:40:22:895 MST] 0000001a SystemOut O 2017-04-03 06:40:22,895 [RPCWorkManager : 118] [ ] [ ] [ ] ( internal.async.Agent) INFO - System date: Mon Apr 03 06:40:22 MST 2017 Total memory: 2,147,483,648 Free memory: 1,181,676,120 Requestor Count: 21 Shared Pages memory usage: 0%
[4/3/17 6:50:22:896 MST] 0000001a SystemOut O 2017-04-03 06:50:22,896 [RPCWorkManager : 126] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Mon Apr 03 06:50:22 MST 2017 Total memory: 2,147,483,648 Free memory: 692,979,320 Requestor Count: 21 Shared Pages memory usage: 0%
[4/3/17 7:00:22:897 MST] 0000001a SystemOut O 2017-04-03 07:00:22,897 [RPCWorkManager : 117] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Mon Apr 03 07:00:22 MST 2017 Total memory: 2,147,483,648 Free memory: 1,140,859,464 Requestor Count: 21 Shared Pages memory usage: 0%
[4/3/17 7:10:22:898 MST] 0000001a SystemOut O 2017-04-03 07:10:22,898 [RPCWorkManager : 119] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Mon Apr 03 07:10:22 MST 2017 Total memory: 2,147,483,648 Free memory: 652,659,240 Requestor Count: 21 Shared Pages memory usage: 0%
[4/3/17 7:15:59:705 MST] 0000001a SystemOut O 2017-04-03 07:15:59,705 [ WebContainer : 0] [TABTHREAD4] [ ] [GPSAPOINTER:01.01.01] (s.generated.gpsa_xxxxgpsautils) INFO xxxxxxxxx| Proprietary information hidden 0060441 - Log D_DialerInformation Page
[4/3/17 7:15:59:705 MST] 0000001a SystemOut O 2017-04-03 07:15:59,705 [ WebContainer : 0] [TABTHREAD4] [ ] [GPSAPOINTER:01.01.01] (s.generated.gpsa_xxxxpsautils) INFO xxxxxxxxx| Proprietary information hidden 0060441 - ### StartLog D_DialerInformation Page#####
Thank you
Accepted Solution
Pegasystems Inc.
US
Watch out for potential native memroy leak if the webcontainer thread number goes beyond 300.
http://www-01.ibm.com/support/docview.wss?uid=swg21368248
Pegasystems Inc.
AU
Hi Sami,
The http requests will eventually arrive in the App Server, and will get assigned to a thread in the App Server's threadpool. It is indeed possible to have many webcontainer threads running for the same requestor based on the type of the request.
Verify what each of these requesters doing by reviewing these in SMA. It is possible to have many threads created for the same requestor.
Regards,
Basavaraj Kadakol
Accepted Solution
Pegasystems Inc.
US
Watch out for potential native memroy leak if the webcontainer thread number goes beyond 300.
http://www-01.ibm.com/support/docview.wss?uid=swg21368248