Hi,

I am trying to remote execute a java program without success.

The JVM is crashing with an java.lang.OutOfMemoryError only seconds after the job starts. This is the output:


#
# An unexpected error has been detected by Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 142576 bytes for Chunk::new. Out of swap space?
#
# Internal Error (allocation.cpp:218), pid=42812, tid=37692
# Error: Chunk::new
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.2-b01 mixed mode windows-amd64)
# An error report file with more information is saved as:
# D:\APPSYS\ODI\TLM-PricingBatchProcess\TLM-PricingBatchProcess\hs_err_pid42812.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp 
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Have you guys seen before this behavior??

Hi Adarve,

unfortunately we have no experience about that. We tried to do a search about this problem but found nothing. Perhaps it has something to do with java config. Perhaps you can supply the config path in the remote exec path some way (because maybe it has some trouble locating it)?

---

Hi,

Thanks for the quick response.

My config for the process is as follows. I have a myexecute.bat file containing:

D:\Appsys\Java\jre6\bin\java -Xmx256m -Xms64m -jar TLM-PricingBatchProcess.jar %1 %2

When running this myexecute.bat in the machine, it runs as expected.

However, when setting up the remote execute I get the JVM crash.

I have tried many combinations to try to make it work: with and without -X parameters, with and without classpath, with and without .bat, ...

It seems clear from the error output that the java process starts running, but it dies when it tries to allocate a chunk of swap space.

I am a little bit lost here. Could it be that the WMI process cannot run the java?? I don't see a lot of java entries in the forum ...

Cheers.

Try writing the full path for the jar in the batch file so it matches the remote server instead of just writing the name of the file.

---

Hi Henrik,

That doesn't seem to be the problem. The process starts running and I see the output for a couple of seconds until the JVM crashes. And again, running locally in cmd works perfectly.

I wonder if we can replicate with a small java program.

Do you have any ideas?

Please make the smallest java app that just writes to the console to see if that causes a problem.

---

Hi Henrik,

I set up the following experiment to run a simple fibonacci java program

myexecute.bat contains:
D:\Appsys\Java\jre6\bin\java.exe -Xmx512m -Xms64m -Xrs -cp D:\Appsys\ODI\TLM-PricingBatchProcess\TLM-PricingBatchProcess\Fibonacci.jar Fibonacci %1 >> %2

The remote execute executes myexecute.bat with parameters 1000 and fibonacci.out for the output.

When I run the task, the program has time to print around 50 fibonacci numbers before getting stuck. It never finishes but it seems to be using cpu according to ProcessExplorer.

When I run the program without parameters -Xmx512m -Xms64m -Xrs it complains it cannot get any memory.

Could you reproduce??