Whilst trying to apply a WAS 6.1 fixpack, I kept seeing this error: -
despite trying various options, including: -
update.exe -is:javahome "c:\Lotus\Mashups\AppServer\java\jre"
and: -
update.exe -is:javahome "c:\WebSphere\AppServer\java\jre"
In the end, I created a log file using the command: -
update.exe -is:javahome "c:\WebSphere\AppServer\java\jre" -is:log c:\foobar.txt
This log file showed a series of messages: -
...
Searching for Sun Java 1.4.X for Windows using path hints
Check path hint Relative C:\Lotus\Mashups\AppServer\updateinstaller\.\java
Verifying JVM at C:\Lotus\Mashups\AppServer\updateinstaller\.\java\bin\java.exe
for JVM: Sun Java 1.4.X for Windows
C:\Lotus\Mashups\AppServer\updateinstaller\.\java\bin\java.exe does not exist
Check path hint Relative C:\Lotus\Mashups\AppServer\updateinstaller\.\java\jre
Verifying JVM at C:\Lotus\Mashups\AppServer\updateinstaller\.\java\jre\bin\java.exe
for JVM: Sun Java 1.4.X for Windows
C:\Lotus\Mashups\AppServer\updateinstaller\.\java\jre\bin\java.exe does not exist
Check path hint Relative C:\Lotus\Mashups\AppServer\updateinstaller\..\java
Verifying JVM at C:\Lotus\Mashups\AppServer\updateinstaller\..\java\bin\java.exe
for JVM: Sun Java 1.4.X for Windows
...
which suggested, to me, that the fixpack installation requires JVM 1.4.X whereas I'm using JVM 1.5.0.
On further reflection, I realised that I was trying to use a WAS 6.0 Update Installer to update my WAS 6.1 instance.
Can you say "Doh" ? I bet you can ....
In the meantime, I'm downloading the correct Update Installer from here.
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Note to self - use kubectl to query images in a pod or deployment
In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
1 comment:
Thanks. It helped me a lot.
M.
Post a Comment