RE: Error launching java ... unable to open jars.cfg -- JAVA400-L

After rereading the error message it seems that the JVM invoked is the 32
bit Java 6 (without looking at the java.home property), which then tries to
locate the jars it needs (looking at java.home).

So, the facility _we_ need - namely being able to specify the JVM in
SystemDefault.properties like for Classic - is not present.

Would be really nice to have. We currently jump through hoops to get the
JAVA_HOME environment variable set on a JAR-file specific manner before
invoking the JVM and it would be great to have a clean and simple IFS-based
solution.

/Thorbjørn

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Dan Kimmel
Sent: 25. november 2013 19:47
To: Java Programming on and around the IBM i
Subject: RE: Error launching java ... unable to open jars.cfg

You raise a good point. Why would Java5 have loaded for David at all?

According to this document setting the java.home property in
SystemDefault.Properties file may cause the JVM to not function at all.
https://www-304.ibm.com/support/docview.wss?uid=nas8N1017748. So I guess
something pays attention to it, but it IS NOT the way one should work.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Thorbjørn Ravn Andersen
Sent: Monday, November 25, 2013 12:03 PM
To: 'Java Programming on and around the IBM i'
Subject: RE: Error launching java ... unable to open jars.cfg

Just to be in the clear. The java.home property is told to be "output

only"

in the V6R1 documentation
(http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/topic/rzaha/sysprop2
.ht
m)
and also in the V7R1 (checked in the PDF).

Does this mean that this is unsupported behavior that just happens to
work, or has this been added since the documentation was written?

It would help us a lot if this was a supported feature.

/Thorbjørn

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: 25. november 2013 17:34
To: Java Programming on and around the IBM i
Subject: RE: Error launching java ... unable to open jars.cfg

Remember that the J9 JVM's only recognize the version from whatever
the JAVA_HOME environment variable contains. In truth, it's the java
command in qshell that does the version selection and after V6R1, it
no longer pays any attention to the java.version set in the command
line. There are several ways to set JAVA_HOME. One is the
SystemDefault.Properties file as you discovered. The
SystemDefault.properties file in your home directory is high in the
precedence list and will override whatever was in JAVA_HOME before the
call to the java command.

Notice that there's a symlink at /QIBM/ProdData/Java that points to
/QOpenSys/QIBM/ProdData/JavaVM to make older JAVA_HOME settings work.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Monday, November 25, 2013 9:40 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Error launching java ... unable to open jars.cfg

On 11/23/2013 6:59 PM, David Gibbs wrote:

----------
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/bin/java -version
getBootClasspath failed to open file

java.home=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/lib/jars.cfg -

A

file or directory in the path name does not exist.

JVMJ9VM015W Initialization error for library jclscar_24(2):

getBootClasspath returned NULL

Unable to create Java Virtual Machine.

I figured out the problem ... I had a SystemDefault.properties file
in my home directory and it contained:
java.home=java.home=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit

(not a typo in the email, thatis 'java.home=java.home...'

Which, apparently, causes Java all sorts of problems.

david

--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding a metric century (100 km / 62 miles) in the 2014
Chicagoland Tour de Cure to raise money for diabetes research,
education,

and advocacy.

Sponsor me by visiting http://archive.ridewithdavid.com. Any amount is
appreciated.
--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/java400-l.

--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.

--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.

--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.