Fix (APAR):  JR31778

Status:  Fix

Release:  6.0.2.5

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  8361

Date: 2009-03-03

Abstract:  ServiceExpirationRuntimeException is not being handled properly.

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

ERROR DESCRIPTION:                                              
In WPS 6.0.2.5 a ServiceRuntimeTimeoutException is thrown in    
the logs, although there is a try-catch block sorrounding the   
wait for reply. This exception is not thrown in WPS versions    
below 6.0.2.5.                                                  
                                                                
This seems to be a regression caused by JR28770                 
                                                                
Exception:                                                      
[12/5/08 10:19:12:500 CET] 00000064 ExceptionUtil E             
CNTR0020E: EJB threw an unexpected (non-declared) exception     
during invocation of method                                     
"transactionNotSupportedActivitySessionNotSupported" on bean    
"BeanId(HelloWorldModuleApp#HelloWorldModuleEJB.jar#Module,     
null)".                                                         
Exception data:                                                 
com.ibm.websphere.sca.ServiceTimeoutRuntimeException: A         
response does not arrive within the designated wait time. Please
adjust the timeout parameter value for the invokeResponse()     
invocation, or the                                              
Transaction Manager timeout setting if longer wait time is      
needed.                                                         

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 WebSphere Process Server v6.0.2.5,
v6.1.0.X, and v6.1.2.X users.

PROBLEM DESCRIPTION:
ServiceExpirationRuntimeException is
not being handled properly.

RECOMMENDATION:
None

ServiceExpirationRuntimeException is not handled properly due
to code changed related to JR28770.

PROBLEM CONCLUSION:                                             
Installing this interim fix will resolve the problem            
reported.                                                       


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: