Java SDK packaging issue when upgrading from v5.0.2 directly to v5.0.2.6
 Technote (troubleshooting)
 
Problem(Abstract)
When upgrading WebSphere® Application Server from v5.0.2 directly to v5.0.2.6, certain JAR files do not get updated properly. This causes the server load to increase, and if you are using light weight processes (LWP), this could cause the JVM™ to continuously create new LWP. On Solaris™ Operating System, you can monitor the LWPs using prstat -p pid. Use of LWP probably means a steady creation and destruction of JVM threads.
 
Cause
ibmtools.jar, ibmorb.jar and ibmext.jar are not packaged properly with Cumulative Fix 6, 7 or 8.
 
Resolving the problem
There are two solutions to this problem.
  1. Remove Cumulative Fix 6 and install Cumulative Fix 4. Then, reinstall Cumulative Fix 6. Cumulative Fix 4 contains the properly-packaged JVM to avoid this issue. Cumulative Fix 6 does not update the files when reinstalling because the files show that they have been upgraded.

  2. Leave Cumulative Fix 6 installed and install the latest Java™ SDK for the operating system in use.

    http://www.ibm.com/support/docview.wss?&context=SSEQTP&q1=cumulative+JDK+windows&uid=swg24007622&loc=en_US&cs=utf-8&lang=en

PQ95139 was opened for this issue.

 
Related information
5.0.2 Cumulative Fix for SDKs
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Windows
Software version: 5.0.2.8
Software edition:
Reference #: 1181871
IBM Group: Software Group
Modified date: Oct 13, 2004