JR55539: THE IBM PROCESS PORTAL INDEX CAN FALL OUT OF SYNC WITH BPM TASK AND INSTANCE DATA LEADING TO WSVR0605W OR OUTOFMEMORYERROR

8.5.7.0-WS-BPM-IFJR55539
8.5.0.1-WS-BPM-IFJR55539
8.5.6.2-WS-BPM-IFJR55539
8.5.0.2-WS-BPM-IFJR55539
bpm.8570.cf2016.06.delta.repository.1of2
bpm.8570.cf2016.06.delta.repository.2of2
8.5.5.0-WS-BPM-IFJR55539

APAR status

• Closed as program error.

Error description

• As process instances and tasks are created and updated, they are
  indexed so they can be retrieved efficiently and displayed when
  you perform a quick search for instances or tasks in IBM
  Process Portal. Transaction timing issues in the Process Portal
  indexing daemon, however, can cause updates to the index to be
  missed, which, in turn, can prevent some instances and tasks
  from being retrieved and displayed when you use a quick search.
  These issues can also affect how data is displayed in the
  Processes, Process Performance, and Team Performance dashboards
  in Process Portal because these dashboards also use the index to
  efficiently retrieve and display data.
    The Lucene index commit time stopped refreshing then we have
  observed the issues in process portal where the completed
  'tasks' are appearing as still 'open'.
  Using Index Diagnostic utility we have found that the Lucene
  Index is not updating with database. We have restarted the
  JVM's couple of times and it didn't resolve the issue.
     There may be hung threads with this java stack.
  .
  "WebContainer : 1" J9VMThread:0x00000000065A1800,
  j9thread_t:0x00007FE920C9D4D0,
  java/lang/Thread:0x000000010F2521D8,
  state:P, prio=5
      (java/lang/Thread getId:0x139, isDaemon:true)
      (native thread ID:0xBBE4, native priority:0x5, native
  policy:UNKNOWN, vmstate:P, vm thread flags:0x00020001)
      (native stack address range from:0x00007FE92AF4E000,
  to:0x00007FE92AF8F000, size:0x41000)
    CPU usage total: 81.553952836 secs
  Parked on:
  java/util/concurrent/Semaphore$NonfairSync@0x0000000148170548
  Owned by: <unknown>
    Heap bytes allocated since last GC cycle=0 (0x0)
    Java callstack:
        at sun/misc/Unsafe.park(Native Method)
        at
  java/util/concurrent/locks/LockSupport.park(LockSupport.java:182
  )
        at
  java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAndChe
  ckInterrupt(AbstractQueuedSynchronizer.java:822)
        at
  java/util/concurrent/locks/AbstractQueuedSynchronizer.doAcquireS
  hared(AbstractQueuedSynchronizer.java:952)
        at
  java/util/concurrent/locks/AbstractQueuedSynchronizer.acquireSha
  red(AbstractQueuedSynchronizer.java:1272(Compiled Code))
        at
  java/util/concurrent/Semaphore.acquireUninterruptibly(Semaphore.
  java:320)
        at
  com/lombardisoftware/component/coachng/gen/CoachGeneratorContext
  Manager.getAndLockContext(CoachGeneratorContextManager.java:75)
        at
  com/lombardisoftware/component/coachng/gen/CoachGenerator.genera
  teInternal(CoachGenerator.java:199)
        at
  com/lombardisoftware/component/coachng/gen/CoachGenerator.genera
  te(CoachGenerator.java:58)
     There may also be OutOfMemoryErrors allocating a large
  com/ibm/bpm/search/instance/search/InstanceListCollector.  This
  may be 3gb in size.  The java stack on the OutOfMemoryError
  would look like
  [4/25/17 12:22:47:717 EDT] 00000263 wle           E
  CWLLG2015E:  An unexpected runtime exception occurred. See
  exception for more details.  Error: Java heap space.
                                   java.lang.OutOfMemoryError:
  Java heap space
   at
  org.apache.lucene.util.PriorityQueue.<init>(PriorityQueue.java:6
  4)
   at
  com.ibm.bpm.search.instance.search.InstanceListCollector$Instanc
  eListTopQueue.<init>(InstanceListCollector.java:382)
   at
  com.ibm.bpm.search.instance.search.InstanceListCollector.<init>(
  InstanceListCollector.java:123)
   at
  com.ibm.bpm.search.instance.search.InstanceListItemSearchImpl.se
  archInstanceListItemsTopN(InstanceListItemSearchImpl.java:141)
   at
  com.ibm.bpm.dashboards.data.InstanceListItemHelper.retrieveInsta
  nceList(InstanceListItemHelper.java:81)
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM) Advanced
  IBM BPM Standard
  IBM BPM Express
  

Local fix

•    See this dwAnswers post
  https://developer.ibm.com/answers/questions/209176/how-to-invest
  igate-and-solve-a-portal-index-out-of.html
  

Problem summary

• No additional information is available.
  

Problem conclusion

• A fix is available for IBM BPM V8.5.7.0 that makes indexing
  fully transactional, ensuring that the index remains in sync
  with the IBM BPM instance and task data.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR55539:
  
  1. Select IBM Business Process Manager with your edition 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 JR55539, 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

• Not applicable
  

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 STANDARD

• Fixed component ID

  5725C9500

Applicable component levels