Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as new function.
Error description
Upgrade-profile fails with NoClassDefFoundError exception on Solaris operating systems during migration of WebSphere Portal 6.1 on WebSphere Application Server 7.0 to WebSphere Portal 8.0. Scenario: - install target system (WebSphere Portal 8.0) - delete profile - create new profile - perform WASPreUpgrade - perform WASPostUpgrade - perform upgradeConfigEngine - start upgrade-profile
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Upgrade-profile fails on Solaris * * during migration of IBM WebSphere * * Portal 6.1 to WebSphere Portal 8.0. * **************************************************************** * RECOMMENDATION: * **************************************************************** During migration of WebSphere Portal 6.1 to WebSphere Portal 8.0, upgrade-profile fails with NoClassDefFoundError exception on Solaris. Scenario: - install target system (WebSphere Portal 8.0) - delete profile - create new profile - perform WASPreUpgrade - perform WASPostUpgrade - perform upgradeConfigEngine - start upgrade-profile The problem was due to a missing reference to the Java endorsed directory in the shell script that launches admin listener.
Problem conclusion
The shell script that launches the admin listener was modified to include the missing reference to Java endorsed directory. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.01. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Make the following changes to WAS_HOME/bin/launchWsadminListener.sh Steps: 1. Find the following line -Dws.ext.dirs="$WAS_EXT_DIRS" \ 2. Add the following line after the line found in step 1 -Djava.endorsed.dirs="$WAS_ENDORSED_DIRS" \
Comments
APAR Information
APAR number
PM41520
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-14
Closed date
2011-08-04
Last modified date
2011-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
27 October 2021