IBM Support

JR56965: UNNECESSARY DATA IS TRANSFERED TO IBM PROCESS PORTAL THAT INCREASES THE BPDINSTANCE LOCK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a user claims a task in IBM Process Portal, more data than
    required in the UI is fetched from the IBM Business Process
    Manager (BPM) server.
    
    Because this additional data includes process instance
    data,additional database locks are requested.  If multiple
    users work on tasks of the same business process definition
    (BPD) instance in parallel, the potential for conflicting
    attempts to get the required database lock on the
    LSW_BPD_INSTANCE table increases and might lead to lock request
    timeouts. You might see exceptions like
    
    110 RestHelper    3   Encountered exception has message:
    PreparedStatementCallback; SQL [SELECT BPD_INSTANCE_ID FROM
    LSW_BPD_INSTANCE WITH (ROWLOCK,UPDLOCK) WHERE BPD_INSTANCE_ID =
    ?]; Lock request time out period exceeded.; nested exception is
    com.microsoft.sqlserver.jdbc.SQLServerException: Lock request
    time out period exceeded.
    
    com.lombardisoftware.core.TeamWorksException:
    PreparedStatementCallback; SQL [SELECT BPD_INSTANCE_ID FROM
    LSW_BPD_INSTANCE WITH (ROWLOCK,UPDLOCK) WHERE BPD_INSTANCE_ID =
    ?]; Lock request time out period exceeded.; nested exception is
    com.microsoft.sqlserver.jdbc.SQLServerException: Lock request
    time out period exceeded.
     at
    com.lombardisoftware.core.TeamWorksException.asTeamWorksExceptio
    n(TeamWorksException.java:136)
     at
    com.lombardisoftware.bpd.runtime.engine.util.LockBPDInstanceComm
    and$1.doInTransaction(LockBPDInstanceCommand.java:75)
     at
    com.lombardisoftware.server.core.TXCommand$2.call(TXCommand.java
    :85)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt$3.doInTransaction(ProgrammaticTransactionSupport.java:500)
     at
    org.springframework.transaction.jta.WebSphereUowTransactionManag
    er$UOWActionAdapter.run(WebSphereUowTransactionManager.java:306)
     at
    com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUO
    W(EmbeddableUOWManagerImpl.java:791)
     at
    com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(E
    mbeddableUOWManagerImpl.java:370)
     at
    org.springframework.transaction.jta.WebSphereUowTransactionManag
    er.execute(WebSphereUowTransactionManager.java:252)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt.executeInNewTransaction(ProgrammaticTransactionSupport.java:4
    88)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt.execute(ProgrammaticTransactionSupport.java:349)
     at
    com.lombardisoftware.server.core.TXCommand.executeInDeadlockRetr
    yLoop(TXCommand.java:83)
     at
    com.lombardisoftware.bpd.runtime.engine.util.LockBPDInstanceComm
    and.execute(LockBPDInstanceCommand.java:81)
     at
    com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.evaluateExpression
    (BPDMappingUtils.java:1730)
     at
    com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.describeBPDInstanc
    e(BPDMappingUtils.java:362)
     at
    com.ibm.bpm.rest.impl.process.BusinessProcessDefinitionResource.
    getBPDInstanceDetails(BusinessProcessDefinitionResource.java:288
    )
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:60)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
    
    in the IBM BPM logs or trace files.
    

Local fix

Problem summary

  • If multiple users work on tasks of the same BPD instance in
    Process Portal, the performance might decrease because of lock
    request timeouts for the BPDInstanceLock.
    

Problem conclusion

  • A fix that avoids sending unnecessary data to Process Portal,
    eliminating the need for database locks on the process instance
    in this scenario, will be available on request from BPM level
    3 support on top of IBM BPM 8.5.6.0 cumulative fix 2, IBM BPM
    8.5.7.0 cumulative fix 2016.06 and will be included in IBM BPM
    8.5.7.0 cumulative fix 2017.03
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR56965

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-08

  • Closed date

    2017-01-12

  • Last modified date

    2017-01-12

  • 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

  • R856 PSY

       UP

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 January 2017