|
Problem |
WSADMIN Client-only installation for version 5.0 is
installed and works properly. However, after applying Fix Pack 2, the
stand-alone WSADMIN client does not start. |
|
Cause |
Fix Pack 2 does not install all of the proper jar files
required for the stand-alone WSADMIN client to start. |
|
Solution |
After installation of Fix Pack 2 for V5.0, the following
error message occurs when trying to start the stand-alone WSADMIN client:
[root@tom was5]# /usr/IBMWebAS5/bin/wsadmin.sh -p
wsadmin.qa.properties
java.lang.reflect.InvocationTargetException:
java.lang.ExceptionInInitializerError:
java.util.MissingResourceException: Can´t find bundle for base name
com.sun.security.auth.Resources, locale en_US
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.ja
va:724)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:695)
at
java.util.ResourceBundle.getBundle(ResourceBundle.java:558)
at
javax.security.auth.Subject.<clinit>(Subject.java:83)
com.ibm.ws.security.auth.SubjectHelper.createSubjectFromWSCredential(Sub
jectHelper.java:75)
com.ibm.ws.security.auth.SubjectHelper.createBasicAuthSubject(SubjectHel
per.java:244)
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminC
lientFactory.java:321)
com.ibm.ws.scripting.CommonScriptingObject.connectToAdminService(CommonS
criptingObject.java:117)
com.ibm.ws.scripting.CommonScriptingObject.<init>(CommonScriptingObject.
java:99)
com.ibm.ws.scripting.AdminControlClient.<init>(AdminControlClient.java:1
52)
com.ibm.ws.scripting.AbstractShell.createControlClient(AbstractShell.jav
a:869)
at com.ibm.ws.scripting.AbstractShell.run(AbstractShell.java:1526)
at
com.ibm.ws.scripting.WasxShell.main(WasxShell.java:805)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
The work-around requires that you have access to a fully-functional
WebSphere® Application Server V5.0.2 system. The operating system does not
matter. The required JAR files are operating system independent.
Copy the following jar files from the V5.0.2 full installation system to
the WSADMIN Client-only installation:
$JAVA_HOME/java/jre/lib/ext/jaas.jar
install_root /java/jre/lib/ext/jaas_lm.jar
install_root /lib/libjaas.so (.so for linux, and .sa for AIX, or
try /java)
install_root /lib/workspace.jar
install_root /lib/runtimefw.jar
install root /lib/deployutils.jar
Also copy the *.component files for each jar file from
WAS_HOME/properties/version directory
install_root /properties/version/prereq.jaas.component
install_root /properties/version/workspace.component
install_root /properties/version/runtime.fw.component
install_root /properties/version/deployutils.component
In the future, when installing fix packs, cumulative fix packs and ifixes
that are reliant on these component files, the updates occur correctly.
Before copying the workspace.jar, verify that
com/ibm/ws/sm/workspace/migration/MOFContext
is in the workspace.jar. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|