Linux-Java-WebSphere Odd Installs
Doug Marker
different Linux distributions.
RedHat 6.1 and Caldera OL 2.2
One very odd test we conducted was that after failing to get WebSphere
to install using jdk117_v3 with native (or green) threads we switched back
to IBM jdk116 and this worked (as we have documented in prior posts).
As an experiment just now, we tried installing WebSphere again but with jdk117_v3 and without uninstalling the previous WAS install (in other words we did install 1 with jdk116, then switched to jdk117_v3 and installed again on top of the existing install), the second install using jdk117_v3 went all the way through without failure. We did of course had to go into the httpd.conf file and remove the duplicate entries. But the odd thing here is that it worked.
If we de-install WebSphere and try to re-install using jdk117_v3 it fails and we have to switch to jdk116 to get the 1st install to work.
We tried this with the ose.outofproc.transport.type=local
(changing the param to remote didn't seem to solve the above odd behaviour).
We are hoping someone from the WebSphere team can cast some light on this odd behaviour.
TurboLinux 3.6
NOTE: installing WebSphere on TurboLinux 3.6 (a glibc2.0 based system)
does *not* exhibt the above odd behaviour but will install quite cleanly
with jdk117_v3 from scratch.
Any clues as to why WebSphere exhibits this odd behaviour would be most welcome.
Doug Marker
(ITSO Linux Project)
Doug Marker
There is *no* way we could get this to work on a fresh RedHat install - two of us tried 12 such installs on 5 different computers so we know it didn't work.
We only ever got the 1st install to work with IBM jdk116 with THREADS_FLAG=native
Hmmmmmmmmm
Doug
Suzy Robinson
does the configurator (usually http://your_linux_machine:9527) function
correctly ? What happens if you try to look at your JVM settings ????
Suzy Robinson
PERCULA consulting GmbH
su...@percula.com
http://www.percula.com
Doug Marker
Hi Suzy,
On a clean RedHat 6 install and with jdk117_v3 we were getting an error
during WebSphere install right at the point where it starts to copy files
(the error was (and still is) an IOException the text says unable to write
unist.zip file.
I just did a complete de-install of WebSphere on another machine (same as
the one mentioned in the first post)
set the Java to jdk117_v3 (which I reinstalled again from scratch with the
native-Threads pack)
set /etc/profile to
JAVA_HOME="/usr/lib/jdk117_v3"
PATH="$PATH:$JAVA_HOME/bin"
THREADS_FLAG="native"
export JAVA_HOME THREADS_FLAG
and as always the install fails
As soon as I change
JAVA_HOME="./usr/lib/jdk116" (IBM's jdk for Linux)
It installs completely and succesfully
have you actually got it to install and the admin to work all on one Linux
box and just using jdk117_v3 ???
Cheers
Doug
Doug Marker
Doug Marker wrote:
>
>
> On a clean RedHat 6 install and with jdk117_v3 we were getting an error
> during WebSphere install right at the point where it starts to copy files
> (the error was (and still is) an IOException the text says unable to write
> unist.zip file.
>
unist.zip file. should read uninst.zip
Suzy Robinson
I followed your instructions (install with JDK1.1.6, IBM) and, having
confirmed that Apache (IBM's version) would not start, switched to Blackdown
and manually edited bootstrap.properties - then decided today to take a look
at the config applet (server:9527) from a Netscape 4.5.1 running on NT and saw
that aside from 'change password', none of the functions worked correctly -
the applet appears to timeout when trying to contact the server, although the
'display connection manager pool' worked maybe once. Hmmm....
Suzy