JR44480: SIGNIFICANT PERFORMANCE DEGRADE WHILE TOOLKIT UPDATE AFTER BPM 8.0 MIGRATION.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Customer has migrated from BPM Advanced
    v7.5.0.1 to v8.0. In process designer when customer tries to
    update the v7.5.0.1 toolkits to v8.0, it takes about an hour
    for the updates the finish.
    

Local fix

  • Need ifix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Customer who wants to update the v75        *
    *                  toolkits to v80 toolkits.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Customer has migrated from BPM          *
    *                      Advanced v7.5.0.1 to v8.0. In process   *
    *                      designer when customer tries to         *
    *                      update the v7.5.0.1 toolkits to v8.0,   *
    *                      it takes about an hour for the          *
    *                      updates to finish.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Looking at the instrumentation logs, there are numerous calls
    that are taking a long amount of time.
    >> THREAD WebContainer : 8 <<
    09:42:28.982 period 4062ms 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canExecuteTasksActions {
    09:42:28.982    period 4062ms 'Transaction' {
    >> THREAD WebContainer : 8 <<
    09:42:34.935 period 3938ms 'Transaction' {
    09:42:34.966    period 3891ms 'EJB Calls'
    Method=ScoreboardAPICore.getScoreboardContent {
    >> THREAD WebContainer : 1 <<
    09:42:55.404 period 1312ms 'EJB Calls'
    Method=RepositoryServicesCore.canDeleteProject {
    >> THREAD WebContainer : 6 <<
    09:43:01.247 period 1016ms 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canExecuteTasksActions {
    09:43:01.247    period 1016ms 'Transaction' {
    >> THREAD WebContainer : 10 <<
    09:43:05.669 period 2953ms 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canExecuteBpdInstancesActions
    {
    09:43:05.685    period 2937ms 'Transaction' {
    >> THREAD WebContainer : 10 <<
    09:43:10.372 period 1688ms 'EJB Calls'
    Method=PersistenceServicesCore.findByFilter {
    09:43:10.372    period 1688ms 'findByFilter' type=Snapshot {
    >> THREAD WebContainer : 10 <<
    09:43:12.872 period 13172ms 'EJB Calls'
    Method=BPDEngineServicesCore.startBPD {
    Additionally, there are numerous calls that are taking an
    'incomplete'
    amount of time.
    >> THREAD WebContainer : 14 <<
    10:39:08.985 period (incomplete) 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canViewTask {
    10:39:08.985    point 'With retry support'
    10:39:08.985    period (incomplete) 'Transaction' {
    Additionally, there are numerous exceptions in systemOut.log,
    but the 1
    that seems relevant is -
    com.lombardisoftware.core.TeamWorksDecoratingException: at
    com.lombardisoftware.bpd.runtime.engine.BPDEngine.executeTreeNod
    e(BPDEng
    ine.java:367) at
    com.lombardisoftware.bpd.runtime.engine.BPDEngine.resume(BPDEngi
    ne.java:
    142) at
    com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore$4.doEx
    ecuteDur
    ingLock(BPDEngineServicesCore.java:602) at
    com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore$4.doEx
    ecuteDur
    ingLock(BPDEngineServicesCore.java:600) at
    com.lombardisoftware.bpd.runtime.engine.util.LockBPDInstanceComm
    and$1.do
    InTransaction(LockBPDInstanceCommand.java:62)
    Caused by: com.lombardisoftware.server.core.CoreException: at
    com.lombardisoftware.server.core.TaskCore.createTask(TaskCore.ja
    va:1079)
    at
    com.lombardisoftware.server.core.TaskCore.createNewTasks(TaskCor
    e.java:2
    289) at
    com.lombardisoftware.server.ejb.taskservices.TaskServicesCore.cr
    eateTask
    s(TaskServicesCore.java:162) at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.jav
    a:60) at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Accessor
    Impl.java:37)
    

Problem conclusion

  • The problem is likely to happen when user groups have many
    users. The code logic did redundant DB access and invoke other
    activities (sometimes unnecessary) internally. The fix
    optimized the logic from these aspects. The performance
    improvement was impressive (from over an hour to a few
    minutes).
    
    For details of install/uninstall instructions, please check
    the README file which can be downloaded together with the ifix
    from Fix Central.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44480

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-22

  • Closed date

    2013-01-11

  • Last modified date

    2013-01-11

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Business Process Manager Advanced

Software version:

8.0

Reference #:

JR44480

Modified date:

2013-01-11

Translate my page

Machine Translation

Content navigation