Problem description from the customer:

     A service written in pure java (that we call a launcher) forks a computation engine which is effectively a binary written in c. The engine communicates with other process via JNI calls to a java API. This java API itself uses RMI as a communication protocol.

After forking the engine, the java service doesn't communicate anymore with the engine.
The engine role is to receive queries from clients which use the same communication API,parse each of them and post and answer.

We observed that after about 30 - 80 queries the server JVM crashes, but not the client JVM.

We can reproduce the crash with 1.4.2_04, 1.4.2_05 and 1.4.2_06

 The only JVM options are the following :
  -server -Djava.class.path=debug.jar:mxjboot.jar:dbslc.jar:limits.jar -Djava.security.policy=java.policy -XX:PrintCompilation -Xcheck:jni

 Note that I already tried to use memory options such as -Xms256M -Xmx512M, but it apparently had no noticeable effect (i.e the engine did crash and it didn't take longer than usual).

###@###.### 2004-12-09 16:43:56 GMT