Fix (APAR):  PI36134

Status:  Fix

Release:  8.5.5.5,8.5.5.4,8.5.5.3,8.5.5.2

Operating System:  AIX,HP-UX,IBM i,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  1028805

Date: 2019-05-13

Abstract:  nullpointerexception when operating hashmap in destroyrequestcontext

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

ERROR DESCRIPTION:
The following exception thrown during stopping JVM.             
                                                                
[15/02/18 3:31:12:472 JST] 00001f03 LocalExceptio E             
CNTR0020E:                                                      
                                                                
EJB threw an unexpected (non-declared) exception during         
invocation of method "timeout" on Bean                          
"BeanId(..., null)"                                             
java.lang.NullPointerException                                  
at java.util.concurrent.ConcurrentHashMap.put                   
(ConcurrentHashMap.java:1002)                                   
at org.apache.webbeans.context.ContextFactory                   
.getContextsService(ContextFactory.java:82)                     
at org.apache.webbeans.context.ContextFactory                   
.destroyRequestContext(ContextFactory.java:114)                 
at org.apache.webbeans.ejb.WSEJBInterceptor                     
.deActivateContexts (WSEJBInterceptor.java:236)                 
at org.apache.webbeans.ejb.WSEJBInterceptor                     
.callToOwbInterceptors(WSEJBInterceptor.java:143)               

LOCAL FIX:
none                                                            

PROBLEM SUMMARY:

USERS AFFECTED:
 All users of IBM WebSphere Application
Server

PROBLEM DESCRIPTION:
NullPointerException in webbeans
ContextFactory during shutdown

RECOMMENDATION:
None

While shuting down WebSphere Application Server a
NullPointerException may occur in the
org.apache.webbeans.context.ContextFactory due to a race
condition with a request running concurently on one thread is
being terminated while the WebSphere Application Server
shutdown code runs on another thread.

PROBLEM CONCLUSION:
The code has been updated to check if the Context has already   
been destroyed before attempting to deactive a context.         
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.5.5.6.  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: Mark with an X the:
1) Release the fix applies to
2) The Editions that apply
3) And then DELETE THIS NOTE

Fix applies to Editions:
Release 8.5
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ Liberty Core
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

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

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: