|
From: Stas O. <sta...@gm...> - 2008-09-30 19:53:45
|
Hi Leif. Eventually we sorted it out. There were huge mem-leaks which apparently just were more visible with wrapper, as the app run as a background process. Which brings me to my current issue - probably not purely related to wrapper, but perhaps which can be solved with it. I noticed that my app takes about 10% less of CPU when running under wrapper, which (as it's a real time app) immediately visible on the results. I presume that it's because the background processes get less priority then the foreground. My question is, how it's possible to give the app same priority as to the foreground processes? Regards. 2008/9/17 Leif Mortenson <le...@ta...> > Stas, > This is also not something that we normally see. Which process is > consuming the CPU? Is it your Java process? > > A couple years ago another user had a similar problem. It turned out > to be caused by a path problem where a configuration file was failing > to be opened. That was throwing an exception which was being caught > and ignored. Then the whole thing was in a loop without any delays. > The result was that the program thrashed consuming 100% CPU. > > The log information requested in reply to your other email may help > show the cause of this problem as well. > > Cheers, > Leif > > > |