PM95851: OUTOFMEMORY IN COM.IBM.WS.WEBBEANS.SERVICES.JCDICOMPONENTIMPL

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• A heapdump analysis will identify the following leak suspect
  
  939,761,560 (95%) [64] 4
  com/ibm/ws/webbeans/services/JCDIComponentImpl0x4134e938
  877,228,328 (89%) [40] 1 java/util/concurrent/ConcurrentHashMap
  0x41365418
  877,228,288 (89%) [80] 16 array of
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe0d8
  55,573,256 (5%) [32] 2
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe120
  55,573,168 (5%) [524,304] 59,505 array of
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x6c67ea10
  12,000 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x775b1dd0
  11,592 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x72c9aac8
  368 (0%) [24] 1
  org/apache/webbeans/context/creational/CreationalContextImpl
  0x775b1d20
  16 (0%) [16] 2 test/group/test/package/someClassName 0x775b1d08
  12,000 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x743f3348
  11,184 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x6688baf0
  11,184 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x4a1055d8
  11,184 (0%) [24] 3
  java/util/concurrent/ConcurrentHashMap$HashEntry 0x5b3658c8
     There are 59,500 more children
  56 (0%) [24] 2
  java/util/concurrent/locks/ReentrantLock$NonfairSync 0x418fe320
  55,439,640 (5%) [32] 2
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe1a0
  55,259,392 (5%) [32] 2
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe280
  55,173,944 (5%) [32] 2
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe2c0
  55,148,272 (5%) [32] 2
  java/util/concurrent/ConcurrentHashMap$Segment 0x418fe2e0
     There are 11 more children
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using JAX-WS web services.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is a memory leak when releasing   *
  *                      the JAX-WS service instance in the      *
  *                      multiple-threads web services call.     *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  When multiple threads invoke the JAX-WS web services at
  approximately the same time, some service instances were
  stored and never released. Also some other instances were
  called to release more than one times. Thus there is a memory
  leak in the release method when releasing the JAX-WS service
  instance.
  

Problem conclusion

• Fixed this problem to release the JAX-WS service instance
  correctly in the multiple threads web services call. This will
  eliminate the memory leak.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.9, and 8.5.5.2.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP