Re: [Wrapper-user] Jar works with console, throws exceptions when launched via start?

[Leif M. <le...@ta...>]

Stas,
That's great news.   The memory leaks were in the Java code?  What are
you maximum memory settings set to?  Are they low enough that the
entire JVM will fit in memory without any swapping along side the OS
and other apps being used?  Java performs very poorly when its memory
is being swapped out. (Not a Wrapper issue)

About the CPU, I reread this thread but I don't think you ever told me
what platform you are running on.  That will make a big difference.
Under UNIX, there is a setting in the shell script which allows you to
specify a "nice" level to control the priority.
On Windows, it is done using the
wrapper.ntservice.process_priority=NORMAL property.  Please be sure to
read the warnings in the documentation.
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-process-priority.html

Normally on most platforms, the OS gives priority to the Windowing
system and those processes to make them more responsive.  That is why
on UNIX, it is good to run servers in a headless environment.

Cheers,
Leif


On Wed, Oct 1, 2008 at 4:53 AM, Stas Oskin <sta...@gm...> wrote:
> 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
>>
>>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>