RE: POE process getting too busy
Markus Jansen <[email protected]> Mon, 27 Aug 2012 00:27:17 +0200
| Newsgroups | gmane.comp.lang.perl.poe |
|---|---|
| Message-ID | <4682B762ECD8E9428E39B8ED2EEDF3EA48C42C2E33@ESESSCMS0365.eemea.ericsson.se> |
Hi Rocco, thanks for your hints - would it help to start a debuggable run, e.g. with = enbugger and trepan,=20 to find out where the problem happens? Best regards, Markus=20 -----Original Message----- From: Rocco Caputo [mailto:[email protected]]=20 Sent: den 25 augusti 2012 10:37 To: POE Mailing List Subject: Re: POE process getting too busy Since this problem is platform-specific, the best I can manage without acce= ss to the machine is advice. Web searches imply that Solaris may be broken, the program may have run out= of file descriptors, an OS upgrade may have broken compatibility with an o= lder build of Perl, or some other issue: https://community.emc.com/thread/111914 http://dbaspot.com/solaris/242660-high-cpu-utilization-solaris-10-a.html http://www.mail-archive.com/[email protected]/msg04283.html http://developerweb.net/viewtopic.php?id=3D5481 http://www.symantec.com/business/support/index?page=3Dcontent&pmv=3Dprint&i= mpressions=3D&viewlocale=3D&id=3DTECH163245 http://wesunsolve.net/bugid/id/6404383 -- Rocco Caputo <[email protected]> On Aug 21, 2012, at 06:09, Markus Jansen wrote: > Hi, >=20 > thanks a lot for the immediate answer, I also changed the code immediatel= y, and started another long-term test run. > Just found the process 99% busy again - the good news is that the signal = pipe does not seem to be the culprit :-). >=20 > Any other suggestions are highly welcome ... >=20 > Thanks & best regards, > Markus >=20 > -----Original Message----- > From: Tod McQuillin [mailto:[email protected]] > Sent: den 16 augusti 2012 02:46 > To: Markus Jansen > Cc: [email protected] > Subject: Re: POE process getting too busy >=20 > On Wed, 15 Aug 2012, Markus Jansen wrote: >=20 >> I have discovered an annoying phenomenon, where after some while=20 >> (days, weeks) a process (which is part of a multi-server POE network) al= l of a sudden goes berzerk by using all resources of its CPU. >> The good news is that the process itself remains fully functional, but f= rom a system usage/load perspective, the situation is quite intolerable. >=20 > This sounds very familiar to me. >=20 > I encountered a similar problem on solaris and was able to make it stop b= y putting the following line of code at the beginning of my POE program: >=20 > BEGIN { eval "sub POE::Kernel::USE_SIGNAL_PIPE () { 0 }" } >=20 > There seems to be a problem with the signal pipe on some platforms, but I= haven't yet done more research to track down what's going wrong. > -- > Tod