[Wrapper-user] RE: JVM appears hung in Wrapper log file for RMI registry service

[Jindong Li <Jin...@so...>]

Thanks Leif for your prompt response...

I'm just thinking...when Wrapper pings the JVM, if there's any issue with
the ping itself (for example, there isn't any socket available, would that
be considered JVM not responding as well?

Jindong.

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...] 
Sent: Wednesday, November 17, 2004 5:52 PM
To: Jindong Li
Subject: Re: JVM appears hung in Wrapper log file for RMI registry service

Jindong,
In the future PLEASE post to the mailing list and not to me directly.

The log is showing that both the Wrapper and Java processes are failing
to get
enough CPU. The Wrapper is continuing to function correctly, but it is
designed to display warnings when that happens.

Since both processes are failing to get CPU, this means that something else
on the system is consuming all available CPU in a way that is failing to
share
that CPU with other processes.

Version 3.1.2 functions much better on systems under high load. Try
upgrading
to 3.1.2 and then setting the following property:
wrapper.use_system_time=false

3.1.2 has a new optional timing method which has been in since 3.1.0. It is
now quite stable and will be the new default in the next release.

This change should make your application behave a little better, but you
should
figure out what is using all of the CPU?

The occasional startup failures you are seeing are because the Wrapper
is not
getting enough CPU to launch the JVM. I don't think this is a problem with
your application or RMI.

Cheers,
Leif


Jindong Li wrote:

> Hi Leif,
>
> How are you doing?
>
> I have an urgent question, I'm using wrapper to start RMI registry
> service as windows service and all is good. Recently however, we've
> getting error messages in the wrapper log file suggesting the JVM the
> RMI registry is started in appears hung and thus restarted by the
> wrapper automatically.
>
> However the restarted registry service does not have any previously
> bound RMI servers and causing RMI lookup throwing NotBoundException.
>
> Any idea and suggestions would be greatly appreciated!!!
>
> Thanks,
>
> Jindong.
>
> I'm attaching the source code for the RMI registry service code and
> the log file as well.
>
> ------------------------------------------------------------------------
> This e-mail message has been scanned for Viruses and Content and
> cleared by *NetIQ MailMarshal *
> ------------------------------------------------------------------------



##############################################################
This e-mail message has been scanned for Viruses and Contents
##############################################################

##############################################################
This e-mail message has been scanned for Viruses and Contents
##############################################################