[Wrapper-user] (no subject)

[<dp...@ro...>]

Subject: JVM appears hung, and SOMETIMES java class not found



I have had the following problem 4 times since the start of 2005, and I'm
hoping someone can suggest what I should be looking at.

(This situation is in our production environment which has very tight
controls over changes, so I am certain that nothing has changed in the
source, or security between when this works and when it fails)

Frequently, (about once a week) we get the messages
ERROR  | wrapper | date time | JVM appears hung: Timed out waiting for
signal from JVM. ERROR  | wrapper | date time | Java Virtual Machine did
not exit on request, terminated INFO  |jvm 4  |  date  time | Launching a
JVM

and usually the next 2 messages are:

INFO  | jvm   | date time | Wrapper (Version 3.0.3)
INFO  | jvm   | date time |


4 times this year however, we get the following:

ERROR  | wrapper | date time | JVM appears hung: Timed out waiting for
signal from JVM. ERROR  | wrapper | date time | Java Virtual Machine did
not exit on request, terminated INFO  |jvm 4  |  date  time | Launching a
JVM
ERROR  | wrapper | date time | The java class is not found:
com/solcorp/pathfinderwrapper/WrapperStartStopApp

The "Launching a JVM" and "class is not found" messages repeats 5 times,
and then another message, (which I don't have handy right now) indiates
that there have been 5 failed starts in a short period of time, and the
service is stopping.

From here, we have to stop and restart our application.


Why does it successfully restart most of the time, but not all of the
time?

Our envionment:

We have 2 Win2003 servers in a websphere (5.1) cluster.
Both servers have 3 NT services running with the wrapper.
The config files for the wrappers are sitting on a NAS (network attached
storage) drive, and the same files are shared between the 2 servers. (if
your familiar, this is part of an Ingenium instalation, and my expertise
is from the Mainframe world).


Thanks in advance  for any suggestions 

King Walling




-- 
-----------------------------------------------------------
dp...@ro...
-----------------------------------------------------------