On Monday 11 September 2006 12:26, Judson West wrote:
>I am trying to install WebSphere AS ND 5.1 on a SLES9 (SP3) 64-bit server.
>I have the following libraries installed:
>
>IBMJava2-SDK-1.4.2-0.60
>IBMJava2-JRE-1.4.2-0.60
>compat-2004.7.1-1.2
>compat-32bit-9-200407011411
>
>
>During the install, I receive the following message:
>InstallShield Wizard
> Initializing InstallShield Wizard...
> Searching for Java(tm) Virtual Machine...
> ...............A suitable JVM could not be found. Please run the program
>again using the option -is:javahome <JAVA HOME DIR>
>
>It then exits.
>
>I was wondering if it is looking for a Java release that I don't have
>installed? If I do need another Java release, can I install it in addition
>to the release that is already there?
>
>I have successfully installed WAS ND 6.0.2 on this same configuration
>without incident.
I ran into a similar problem when installing WAS 5.1 on an x86 box a while ago
also, but I cannot remember just how I fixed it. Hopefully, the bits I can
remember will help you proceed.
WebSphere ships with a JRE in the installation package, so it should always be
able to find a "suitable JVM". However, the JRE shipped with WebSphere 5.1
on x86 did not work properly. The installer would just hang. Yours exits,
but the cause might be the same: the JRE is not working.
I used the -is:log option of InstallShield, and found that it was trying to
get the version string from the JRE shipped with WAS. I copied that JRE out
of InstallShield's temporary directory and ran strace on it to find out that
it was catching a SIGSEGV somewhere, and its recovery of that looped to cause
the SIGSEGV again, thus the hang.
What I just can't remember is how I fixed that, but perhaps the above
debugging path will get you started. Try to capture the JRE that
InstallShield is trying to use and run it with the -version option. You
should get something like this:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cx3901420-20040626 (JIT enabled:
jitc))
which is the Java version used by WAS 5.1 on both the s390 and x86 platforms.
That is what InstallShield should be looking for. The -is:log output should
say that. If the JRE from InstallShield cannot even report the version
string (as mine could not), that's when you need to resort to strace to find
out what is broken.
Sorry I can't be of more help, but I didn't take notes on how I fixed this
problem and my memory leaks. :-) If the above gets you a bit further and you
post more info, perhaps it will jog my memory.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
