Re: [Wrapper-user] After enabling JMX support, Java Service Wrapper consumes 25% - 30% CPU

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

Joachim,
What version of the Wrapper are you using?

The Wrapper makes itself available for JMX access, but the Wrapper
itself does not ever call any of these APIs  Other than a client
connecting, there is nothing I can think of which would be consuming
CPU.

When you see the high CPU, could you try invoking a few thread dumps.
You can do this when running in a console by hitting CTRL+BREAK on
your keyboard.    If it is eating so much CPU then you should be able
to catch one of the calls in the act to see what is happening.

Please let me know the results.

Cheers,
Leif

On Mon, Aug 22, 2011 at 10:17 PM, Joachim Gruhn <joa...@sn...> wrote:
> Hi all,
>
> i am new to the Java Service Wrapper and have successfuly installed and
> configured Java Service Wrapper on a Windows 2008 Server R2 (8 cores).
> We are using integration method 4.
> After enabling the JMX support in the wrapper.conf with
> wrapper.java.additional.3=-Dcom.sun.management.jmxremote and restarting
> the service the process consumes 25% to 30% of cpu utilization. There is
> no client connected at this point. Disabling the JMX again the process
> consumes up to 7% cpu.
> What could be the reason of such huge cpu consumption with the JMX support?
>
> Best regards
> Joachim