IBM Support

JR51002: USING 'AUTOMATICALLY FLOW TO NEXT TASK' IN COMBINATION WITH 'OPTIMIZE EXECUTION FOR LATENCY' CAUSES TEAMWORKSEXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you specify  'Automatically flow to next task' when you
    create a user task, in combination with 'optimize execution for
    latency' for the business process definition (BPD), you will see
    the following TeamWorksException in SystemOut.log:
    
    [1/14 10:57:13:300 CEST] 000030ce wle           E   CWLLG2229E:
    An exception occurred in an EJB call.  Error: No Thread Control
    Block registered for current thread
     at com.lombardisoftware.core.TeamWorksException.
       asTeamWorksException(TeamWorksException.java:136)
     at com.lombardisoftware.server.ejb.psapi.RoutingAPIFacadeCore.
       completeTaskAndResumeImmediately(RoutingAPIFacadeCore.
       java:229)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke
       (NativeMethodAccessorImpl.java:60)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke
       (DelegatingMethodAccessorImpl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at org.springframework.aop.support.AopUtils.
       invokeJoinpointUsingReflection(AopUtils.java:310)
     at org.springframework.aop.framework.
       ReflectiveMethodInvocation.invokeJoinpoint
       (ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.
       ReflectiveMethodInvocation.proceed
       (ReflectiveMethodInvocation.java:149)
     at com.lombardisoftware.utility.spring.
       TransactionInterceptor$2.call(TransactionInterceptor.java:67)
     at com.lombardisoftware.utility.spring.
       ProgrammaticTransactionSupport.executeWithNoTransaction
       (ProgrammaticTransactionSupport.java:609)
     at com.lombardisoftware.utility.spring.
       ProgrammaticTransactionSupport.execute
       (ProgrammaticTransactionSupport.java:321)
     at com.lombardisoftware.utility.spring.TransactionInterceptor.
       invoke(TransactionInterceptor.java:65)
     at org.springframework.aop.framework.
       ReflectiveMethodInvocation.proceed
       (ReflectiveMethodInvocation.java:171)
     at com.lombardisoftware.utility.spring.CoreEntryInterceptor.
       invoke(CoreEntryInterceptor.java:44)
     at com.lombardisoftware.utility.spring.PSCoreEntryInterceptor.
       invoke(PSCoreEntryInterceptor.java:14)
     at org.springframework.aop.framework.
       ReflectiveMethodInvocation.proceed
       (ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.
       invoke(JdkDynamicAopProxy.java:204)
     at com.sun.proxy.$Proxy85.completeTaskAndResumeImmediately
       (Unknown Source)
     at com.lombardisoftware.server.ejb.psapi.
       RoutingAPIFacadeBean$2.execute(RoutingAPIFacadeBean.java:71)
     ...
    

Local fix

Problem summary

  • The 'optimize execution for latency' feature introduces a new
    infrastructure that must be initialized on each thread that uses
    it. The 'automatically flow to next task' feature uses a special
    thread on which the 'optimize execution for latency'
    infrastructure is not initialized.
    

Problem conclusion

  • A fix is available for IBM BPM 8.5.5.0 that initializes the
    'optimize execution for latency' infrastructure on the
    'automatically flow to next task' thread. With this fix, using
    both features in combination allows an automatic flow to the
    next user task even if a system task or a decision task is
    between the current user task and the next user task.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR51002:
    
    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 JR51002, 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 number

    JR51002

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-08

  • Closed date

    2014-09-17

  • Last modified date

    2014-09-17

  • 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

  • R855 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":"855","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 September 2014