Re: [Wrapper-user] Wrapper Monopolizes CPU

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

Ben,
I have never seen or heard of any examples of the Wrapper or its
Java component consuming lots of CPU due to the Wrapper.

To confirm, it is the java process and not the wrapper process
that is using up all the CPU.

You might want to try doing some profiling of your JVM to narrow
down the cause. From you classpath, and 
configManager.VPNManagement.RegistrarDaemon
class, it is likely that more is going on in your application than
the loop below.

I have seen cases where the java application is not being configured
as expected when running under the wrapper. An incorrect path
for example. Something like that could cause some thrashing of
an outer loop depending on how the error handling code
was written.

You can review the full command used to launch the JVM by adding
the following to your wrapper.conf
wrapper.java.command.loglevel=INFO

Cheers,
Leif

Ben Leibert wrote:
>
> I’m using version 3.2.3 of the wrapper on SuSe Linux 10.1 alongside 
> version 1.5 of Java. The “top” command shows the wrapper to 
> consistently monopolize the CPU, which I’d ~really~ appreciate help 
> resolving. The code I’m testing with looks as follows:
>
> while(true)
>
> {
>
> System.out.println("This just ran");
>
> Thread.currentThread().sleep(3000);
>
> }
>
> Only when run via the wrapper does this dominate the processor. 
> Neither changing the wrapper.ping.interval nor the priority (nice) 
> properties has had any noticeable affect. My configuration files are 
> included below. Thanks in advance for any help!
>
> Cheers,
>
> Ben
>
(snip)