Cloverleaf process limitation — Any solution ?

It sounds like you may be running up against the licensed thread count unless you have an unlimited license. Check the beginning of your process logs for more information.

Hi mitesh –

for the stats it sounds like the hcimsitutil command would have the info you want. hcimsiutil -dd threadName will give you a bunch of information about thread activity.  there are also tcl commands (msiAttach, msiTocEntry, msiGetStatSample) that you can use to get a keyed list of the thread statistics that appear in the hcimsiutil command.

I’m mostly going to babble out loud some to possibly stimiulate other thoughts perhaps more tangible, so forgive me otherwise.

I first thought it might be a license limitation but not sure since we have unlimited license here.

I also thought license limitation was based on thread count and not process count.

If thread count is hitting a limit and causing a process not to start then I would ask do you have auto-start configured on your threads.

we learned and feel auto-start has more disadvantages than advatages.

We have a standard prohibiting the use of auto start at least in production and have been better off since adopting that practice.

I thought we had significant number of processes running but added them up and only have 113 running right now in production.

That means if there is a 300 something limit wer are a good ways off.

this does make me think you must have hundereds of sites with that many process but then I realized there are shops that over fill sites with process and threads.

That leads me to the next question, if all these process are in one site or a handfull of sites I would say you are fortunate to have gotten as far as you did.

In UNIX/Linux, monitorShmemFile is not a file in the traditional sense. It is a FIFO (First In First Out), also known as a “Named Pipe”.