[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
3744.0. "%MCC-W-THRMAX, maximum thread count reached." by KERNEL::DAVIES () Tue Sep 15 1992 16:00
Hi Chaps,
I have a customer who is running V5.5 VMS and DECmcc V1.2.
He has set up some extensive recording using FCL (via a .COM file).
The recording is set up to poll approximately 11 node4 area routers
for all partitions. From what I understand, it polls all of these
nodes every 30 minutes.
The recording stops after about half an hour with the error:-
%MCC-W-THRMAX, maximum thread count reached.
Can he change any of the MCC logicals to increase the thread count
or is his only option to stagger the polling???.
Would modifying the logical MCC_HISTORIAN_FM_STACK, which is set to
64 by default, make any difference?
Cheers,
Phil Davies. UK Comms TSC
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3744.1 | 500 recordings is a limit | TOOK::SHMUYLOVICH | | Tue Sep 15 1992 19:52 | 8 |
|
The historian background process is able to handle up to 500
active recording requests per domain.
If a bigger number of recording is needed I would recommend to use
more that one domain.
Sam
|
| 3744.2 | more clarification | COMICS::MISTRY | | Thu Sep 17 1992 14:11 | 6 |
| Sam,
Does that mean 1 thread per request.
Bipin.
|
| 3744.3 | recording request = thread in background | TOOK::SHMUYLOVICH | | Mon Sep 21 1992 13:11 | 5 |
|
Yes, the Historian background process creates one thread per recording
request.
Sam
|