JR59159: PERFORMANCE IN THE DESKTOP IBM PROCESS DESIGER IS SLOWER WHEN YOU TRY SEVERAL OPERATIONS WORKING ON A LARGE PROCESS APP

8.5.6.2-WS-BPMPCPD-IFPD59159
bpm.8600.cf2018.03.delta.repository

APAR status

• Closed as program error.

Error description

• If you try several operations in the desktop IBM Process
  Designer that require searching for library objects, such as
  saving, viewing coach, and opening a process app, you might
  encounter slower than expected performance when working on a
  large application. In particular, saving an operation is
  slowest.
  
  Server-side log shows operations completing quickly and much of
  the delay is on the Process Designer side. Javacore from Process
  Designer shows most of the wait is on a hashmap with following
  stack:
  
  3XMTHREADINFO3           Java callstack:
  4XESTACKTRACE                at
  java/util/HashMap.containsValue(HashMap.java:765(Compiled Code))
  4XESTACKTRACE                at
  java/util/HashMap$Values.contains(HashMap.java:1056(Compiled
  Code))
  4XESTACKTRACE                at
  java/util/Collections$UnmodifiableCollection.contains(Collection
  s.java:1 069(Compiled Code))
  4XESTACKTRACE                at
  com/lombardisoftware/client/ae/server/RepositoryServerNodeImpl.f
  indExactLibraryItemIfLazyCached(RepositoryServerNodeImpl.java:22
  11(Compiled Code))
  4XESTACKTRACE                at
  com/lombardisoftware/client/ae/server/RepositoryServerNodeImpl.f
  indLibraryItem(RepositoryServerNodeImpl.java:1201(Compiled
  Code))
  4XESTACKTRACE                at
  com/lombardisoftware/client/ae/server/RepositoryServerNodeImpl.f
  indLibraryItem(RepositoryServerNodeImpl.java:1168(Compiled
  Code))
  4XESTACKTRACE                at
  com/lombardisoftware/client/ae/sm/forms/service/model/variables/
  ServiceVariableParameterAdapter.<init>(ServiceVariableParameterA
  dapter.java:65(Compiled Code))
  

Local fix

Problem summary

• In the desktop Process Designer, when you try to load a library
  item by context, Process Designer tries to see if the context
  must be cached first in a dependency path to a context hash map.
   If the process application has a large dependency tree, this
  hash map will be huge and will slow the lookup because Process
  Designer is looking up the value instead of the key of the map.
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM)
  IBM BPM Express
  

Problem conclusion

• A fix is intended for inclusion in a future release of IBM BPM
  that uses a different hash map with the context as the key for
  the lookup, which is much faster. In addition, the fix also will
   improve the tracing for the
  "com.lombardisoftware.client.ae.server.RepositoryServerNodeImpl=
  all" trace string in the desktop Process Designer.
  

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

• Fixed component ID

  5737A5700

Applicable component levels