JR50302: PERFORMANCE DEGRADES WHEN YOU USE FAILED EVENT MANAGER IN THE ADMINISTRATIVE CONSOLE

8.5.5.0-WS-BPM-IFJR50302
Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Every time you use the failed event manager in administrative
  console, a new temporary workspace directory named
  anonymous######## is created in the
  <DEPOLYMENT_MANAGER_PROFILE>/wstemp directory and is never
  deleted, which can quickly use all the disk space.
  .
   The local file system inodes were exhausted due to
  number anonymous folders created in the wstemp directory of the
  deployment manager.
  .
  Three or more folders of this type are
  created with each call of the FailedEventManager. Each of these
  folders contains about 9000 files and uses about 23 MB.
  .
  .-----------------------------------
     This may cause the ISCAdmin (the WebSphere
  Administrative) console to hang.
  .
     Related to this hang, there may also be an OutOfMemoryError
  on the deployment manager (DMGR) jvm.
  
  .-------------------------------------
  These signatures will appear in a heap dump analysis.  The
  number of workspaces is equivalent to the size of the HashMap
  array.
  2,132,863,136 (21.22%) [32] 14 class
  com/lombardisoftware/core/config/common/LdapOptionsConfig
  0x580f63d50
  |- 2,132,862,728 (21.22%) [32] 71 class
  com/ibm/bpm/config/spi/ConfigurationSpi 0x580084138
     |- 2,132,493,120 (21.22%) [32] 81 class
  com/ibm/bpm/config/util/ws/WccmHelper 0x58008cb58
        |- 2,132,483,592 (21.21%) [32] 61 class
  com/ibm/ws/management/configservice/WorkspaceHelper 0x58070d0f8
           |- 2,124,755,672 (21.14%) [32] 13 class
  com/ibm/ws/sm/workspace/WorkSpaceManagerFactory 0x58070d270
              |- 2,124,754,744 (21.14%) [40] 3
  com/ibm/ws/sm/workspace/impl/WorkSpaceManagerImpl 0x583595748
                 |- 2,124,754,696 (21.14%) [16] 2
  java/util/Collections$SynchronizedMap 0x585295f88
                    |- 2,124,754,680 (21.14%) [48] 1
  java/util/HashMap
  0x585295fa0
                       |- 2,124,754,632 (21.14%) [65,552] 6,709
  array of
  java/util/HashMap$Entry 0x5b2153330
                          |- 1,204,480 (0.01%) [24] 3
  java/util/HashMap$Entry 0x5bad65a20
                          |- 1,204,480 (0.01%) [24] 3
  java/util/HashMap$Entry 0x612af5ea8
                          |- 1,204,480 (0.01%) [24] 3
  java/util/HashMap$Entry 0x6241694d0
                          |- 963,584 (0.01%) [24] 3
  java/util/HashMap$Entry 0x61f1346c8
                          ....over 6000 more children
  
  Expanding the first entry:
  1,204,480 (0.01%) [24] 3 java/util/HashMap$Entry 0x5bad65a20
  |- 963,584 (0.01%) [24] 3 java/util/HashMap$Entry 0x5b4bb6938
     |- 722,688 (0.01%) [24] 3 java/util/HashMap$Entry 0x60c617950
        |- 481,792 (0%) [24] 3 java/util/HashMap$Entry 0x5fdff3ef0
           |- 240,896 (0%) [24] 2 java/util/HashMap$Entry
  0x5e17cd9e0
              |- 240,784 (0%) [88] 14
  com/ibm/ws/sm/workspace/impl/WorkSpaceImpl 0x5e17d4828
  .
  AND
  you may see threads in this stack as well java stack in a
  javacore.
  (entered lock:
  com/ibm/ws/sm/workspace/migration/WSResourceSetImpl@0x0000000074
  8C69F8,
  entry count: 1)
  4XESTACKTRACE                at
  com/ibm/ws/sm/workspace/migration/WSResourceSetImpl.getResource(
  WSResour
  ceSetImpl.java:196(Compiled Code))
  4XESTACKTRACE                at
  com/ibm/ws/management/configservice/WorkspaceHelper.getDocAccess
  orIntern
  al(WorkspaceHelper.java:261(Compiled Code))
  4XESTACKTRACE                at
  com/ibm/bpm/config/util/ConfigHelper.queryObject(ConfigHelper.ja
  va:825(C
  ompiled Code))
  4XESTACKTRACE                at
  com/ibm/bpm/config/util/ConfigHelper.queryObject(ConfigHelper.ja
  va:802(C
  ompiled Code))
  4XESTACKTRACE                at
  com/ibm/bpm/config/util/ConfigHelper.getClusterMembers(ConfigHel
  per.java
  :4815(Compiled Code))
  4XESTACKTRACE                at
  com/ibm/bpm/config/util/ConfigHelper.getMembersFromCluster(Confi
  gHelper.
  java:1146(Compiled Code))
  4XESTACKTRACE                at
  com/ibm/ws/console/wbi/wbifailedeventmanager/jmx/WbiRecoveryMBea
  nHelper.
  getDeScopedRecoveryMBeanFilterString(WbiRecoveryMBeanHelper.java
  :172(Com
  piled Code))
  4XESTACKTRACE                at
  com/ibm/ws/console/wbi/wbifailedeventmanager/jmx/WbiRecoveryMBea
  nHelper.
  isRecoveryAvailable(WbiRecoveryMBeanHelper.java:195)
  4XESTACKTRACE                at
  com/ibm/ws/console/wbi/wbifailedeventmanager/WBIFailedEventManag
  er.getFa
  iledEventCount(WBIFailedEventManager.java:123)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
  *                  Advanced                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Every time you use the failed event     *
  *                      manager in administrative console, a    *
  *                      new temporary workspace directory       *
  *                      named anonymous######## is created in   *
  *                      the                                     *
  *                      <DEPOLYMENT_MANAGER_PROFILE>/wstemp     *
  *                      directory and is never deleted, which   *
  *                      can quickly use all the disk space.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A temporary workspace directory is created and never deleted
  when you use the failed event manager in the administrative
  console.
  

Problem conclusion

• A fix is available for IBM BPM V8.5.0.1 that temporary
  directory is deleted when you use the failed event manager in
  the administrative console.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR50302:
  
  1. Select IBM Business Process Manager and then Advanced from
  the product selector, the installed version to the fix pack
  level, and your platform, and then click Continue.
  
  2. Select APAR or SPR, enter JR50302, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R800 PSY

     UP