|
From: Gil A. <gi...@gi...> - 2005-09-01 21:56:25
|
No, mine up was A LOT, like 100,000 lines in an hour when it was in debug log level. Sounds like you have a different issue. :( -Gil At 01:47 PM 9/1/2005, you wrote: >Hi Gil > > >> I've experienced a similar situation when the output from my Java > process printed A LOT of lines of output to STDOUT/STDERR. > > >> Are you doing anything like that with your application? >Yep. I wouldn't say it's a LOT but maybe a 200 - 300 short lines in about >24 hours. Is that about the same as in your app? > >- Frank > > > >---------- >Von: wra...@li... >[mailto:wra...@li...] Im Auftrag von Gil Adam >Gesendet: Donnerstag, 1. September 2005 22:44 >An: wra...@li... >Betreff: Re: [Wrapper-user] suddenly java.exe consumes 100 percent of free >processor time > >I've experienced a similar situation when the output from my Java process >printed A LOT of lines of output to STDOUT/STDERR. > >Are you doing anything like that with your application? > >-Gil > >At 01:28 PM 9/1/2005, you wrote: >>Hi all >> >>I'm using the Wrapper in a productive environment now for about 10 >>months. So far expect for one problem it runs very fine. >>About 3 times within this periode i had a strange effect. On a W2k3 >>Server Dual Xeon the java.exe suddenly, after a period of some months >>without any problem, consumes constantly 100% of the free processor time. >>It's not that dramatic since it only uses free ressources and doesn't >>block others processes, but however it's not the way it should work. >>The funny thing about it - the Java Application and the Service Wrapper >>both seem to continue working without problem or loss of performance. >>Also memory usage is stable. >>What i can say, is, that my Java Application seems to be in normal state >>as ever, there is no abnormal behaviour, so i guess, it's not the source >>for the effect. Also the logs of the service wrapper look quite normal - >>ping seems to be working constantly and a service restart using indows >>Control Settings/Services works fine. >> >>Does anyone ever had a similar situation? >>Could it be, that the source of the effect is somewhere in the Java part >>of the Service Wrapper? Is there a way to check this? >>Any ideas, hints? >> >>Thanks for your help >>Frank |