[mpich-discuss] Jumpshot and mpich2-1.3.3rc1

[Jain, Rohit]

echo prints this:
/usr/bin/java -Xms32m -Xmx512m -jar /mpich2_debug/install-mpe/mpich2-1.3.3rc1/linux/lib/jumpshot.jar Unknown.slog2

If I set JRE_HOME to earlier used JAVA installation, then Jumpshot starts working.

So,
1) java installed on my machine isn't working with Jumpshot.
gij --version
gij (GNU libgcj) version 3.4.6 20060404 (Red Hat 3.4.6-11)

2) if above is true, does mpich2 provides compatible java version too with its installation? If it doesn't, are there guidelines on compatible JAVA versions?

3) Has JRE env been deprecated, as it doesn't work anymore? 

4) --with-java= option still works with latest release. If used, it picks up default specified version during runtime, instead of machine installed.

Regards,
Rohit


-----Original Message-----
From: mpich-discuss-bounces at mcs.anl.gov [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Nicolas Rosner
Sent: Monday, March 07, 2011 6:02 PM
To: mpich-discuss at mcs.anl.gov
Subject: Re: [mpich-discuss] Jumpshot and mpich2-1.3.3rc1

> From the error message, it seems that issues has to do with either java
> runtime or build environment.

I agree, and it looks like the former is missing or not being pointed
to correctly. What flavor and version of a Java runtime is installed
on that machine?

This is what I see on my system if I replace `Show=""' with
`Show="echo"' on the first line (after the shebang) of the
bin/jumpshot script:

$ jumpshot foobar.slog2
GUI_LIBDIR is set. GUI_LIBDIR = /mpi/lib
/usr/bin/java -Xms32m -Xmx512m -jar /mpi/lib/jumpshot.jar foobar.slog2

What do you get? Keep in mind that the first component should be a
Java runtime (as in the VM binary), not a Java compiler (such as
javac, gcj, etc).

Also note that the script apparently lets you override its
configure-time-found location via env vars, e.g. JAVA_HOME et al.


> Warning: -Xms32m not understood. Ignoring.
> Warning: -Xmx512m not understood. Ignoring.
> Warning: -jar not understood. Ignoring.

This sounds like whatever's being used as the `java' executable
doesn't know about the -jar command line switch. The first two could
be ignored to some extent, but ignoring the third one should indeed be
fatal: among other things ...


> Exception in thread "main" java.lang.NoClassDefFoundError: .mpich2_debug.install-mpe.mpich2-1.3.3rc1.linux.lib.jumpshot.jar

... a pathname to a .jar file is not a class name (although your
`java' should normally be able to deduce the main class from the
manifest within the .jar, if run in -jar mode).


Regards
Nicolás
_______________________________________________
mpich-discuss mailing list
mpich-discuss at mcs.anl.gov
https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss