Fix (APAR):  JR28092

Status:  Fix

Release:  6.0.2.3,6.0.2.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  15661

Date: 2008-01-22

Abstract:  If a service component is implemented synchronously, the ResponseTime data monitor collected is always 0. If a service component is called asynchronously, the TotalResponseTime dat

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

ERROR DESCRIPTION:                                              
Customer is trying to collect statistics of SCA calls (both Sync
and Async) using Performance Monitoring Indicators (PMI) with   
Tivoli Performance Viewer.                                      
                                                                
To reproduce the behaviour:                                     
                                                                
1. Admin Console -> Monitoring and Tuning -> Performance Viewer 
-> View Logs                                                    
                                                                
Import the file that is available at:                           
                                                                
/ecurep/pmr/3/2/32925,033,000/support_files                     
                                                                
Select Performance Modules -> SCAStats.RootGroup -> SCA ->      
com.ibm.xmlns.prod.....GetBanDriverProcessIMAP ->               
MethodInvocation ->                                             
_GetBanInfo_getBanInfo                                          
                                                                
The counters will be displayed in 'Graphical' mode - Please     
select 'View                                                    
Table' to display the data in Tabular mode.                     
                                                                
The counters:                                                   
                                                                
_GetBanInfo_getBanInfo.ResponseTime and                         
_GetBanInfo_getBanInfo.TotalResponseTime                        
                                                                
has 0.00 as the values in a 20 minute capture.                  

LOCAL FIX:                                                      
There is no workaround or Local fix that's available.           

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.2 users who
monitor performance data with performance
monitoring infrastructure.

PROBLEM DESCRIPTION:
If a service component is implemented
synchronously, the ResponseTime data
monitor collected is always 0.
If a service component is called
asynchronously, the TotalResponseTime
data monitor collected is always 0.

RECOMMENDATION:
None

The code did not handle synchronous implementation and
asynchronous call correctly.

PROBLEM CONCLUSION:                                             
Applying this interim fix will resolve the issues of            
synchronous and asynchronous calls.                             


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: