Fix (APAR):  PK38099

Status:  Fix

Release:  6.0.2.19,6.0.2.17

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK38099

Byte size of APAR:  16021

Date: 2007-10-08

Abstract:  Reduce the number of SQL calls executed when the javax.ejb.Timer interface is called from with the "ejbTimeout" method.

Description/symptom of problem:  
 
PK38099 resolves the following problem:

ERROR DESCRIPTION:                                              
Within the execution of the "ejbTimeout" method, the user can   
make calls to the javax.ejb.Timer interface.  Calls made to this
interface may result in an SQL call to the database contain the 
timer data.                                                     
In this fix, some optimization will be made to limit the number 
of SQL calls executed when the calls to the Timer interface are 
made from within the "ejbTimeout" method.                       

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
IBM WebSphere Application Server version 6
users who make use of the javax.ejb.Timer
interface.

PROBLEM DESCRIPTION:
Reduce the number of SQL calls
executed when the javax.ejb.Timer
interface is called from with the
"ejbTimeout" method.

RECOMMENDATION:
None

Within the execution of the "ejbTimeout" method, the user can
make calls to the javax.ejb.Timer interface.  Calls made to
this interface may result in an SQL call to the database
containing the timer data.  Limiting SQL calls when possible
is always a good idea for performance.  Where possible the
data from the SQL call will be cached for the duration of the
ejbTimeout method, thus resulting in a performance enhancement.

PROBLEM CONCLUSION:                                             
In this fix, some optimizations were made to limit the number   
of SQL calls executed when the calls to the Timer interface are 
made from within the "ejbTimeout" method.                       
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpacks 6.0.2.21 and 6.1.0.9.                                  
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
_X_ Application Server (Express or BASE)
_X_ Network Deployment (ND)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_X_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy 6.0.2.17-WS-WAS-IFPK38099.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.0.2.17-WS-WAS-IFPK38099.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (6.0.2.17-WS-WAS-IFPK38099.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.



Additional Information: