JVM termination with standalone oc4j

[peoplesrepublican]

Hi,

We have several (around 15) standalone oc4j instances running on a Sun machine, the details are as follows:

Machine: SunFire V1280 with 8 processors (sun4u sparc) and 24 GB RAM
OS: SunOS 5.9 Generic_117171-02
oc4j version: 9.0.4.0.0

There is also a 10g installation on this machine.

We are finding that quite regularly one or more of the oc4j instances shuts down without warning. the only information in the log files (jms.log, rmi.log etc) is a "Stopped (JVM termination)" message. I cannot find any other logs on the machine which can help me with this error.

I am after one of two things:

1. Potential reasons for this happening (preferably with solutions!)
2. A possible for a log file created by the JVM detailing why it is terminating.

Can anyone help?

Thanks

 

[Diancecht]

Difficult to know. Some posible guidelines:

1.- Check oc4j logs (if there is such a thing)
2.- Check the code for System.exit() calls.

This could be the easy way.

If it happens from time to time, maybe there's a memory leak that make the instances run out of memory. There should be any logs with that info. If not, check if you have any kind of memory usage monitorization.

Cheers,

Dian