Print

---

Hi,

we've seen our R-GMA service go nuts a few times since upgrading to
2.3.1.  I just now caught it in the act: load on the machine was about
150.  Checking, there were an awful lot of 'ps' processes floating
around.  Here is a snippet of the output of pstree:

      ├─java
      ├─crond─┬─86*[crond───sh───sh───edg-rgm+
      │       ├─4*[crond───sh───sh───edg-rgma+
      │       ├─2*[crond───sh───sh───edg-rgma+
      │       ├─5*[crond───sh───sh───edg-rgma+
      │       ├─6*[crond───sh───sh───edg-rgma+
      │       ├─2*[crond───sh───sh───edg-rgma+
      │       ├─4*[crond───sh───sh───edg-rgma+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       ├─5*[crond───sh───sh───edg-rgma+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       ├─2*[crond───sh───sh───edg-rgma+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       ├─crond───sh───sh───edg-rgma-se+
      │       └─crond───sh───sh───edg-rgma-se+


looks like the culprits are:

- edg-rgma-restart
- edg-rmga-service-status
- edg-rgma-servlet-status
- edg-rgma-servlet-monitor

and there are hundreds of processes running that are all trying to stop
tomcat4 ...

anybody else seeing this??

                                JT