IBM Support

JR55136: YOU CANNOT START EXPOSED HUMAN SERVICES IN PROCESS CENTER WHEN THEY ARE NOT RUN FOR A SPECIFIC SNAPSHOT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After you update to IBM Business Process Manager V8.5.6
    cumulative fix 2, an exposed human service that runs in the
    context of a tip snapshot in IBM Process Center fails because of
     an issue with the permissions check.
    
    You see this generic error message:
    
    Error: Ask the administrator to check the SystemOut.log file for
    more information to resolve the error.
    
    If interim fix JR54974 is installed, you also see this message
    in the SystemOut.log file:
    
    wle_portal    E   You are not allowed to execute this item for
    one of the following reasons:
    -The service is not exposed.
    -The snapshot is not active.
    -You do not have permission to run the service.
    
    Because the user is a member of the team associated with the
    exposed service in IBM Process Designer for the process app, he
    or she should be able to run the process app without problems.
    
    Some of the exposed services affected by this problem are
    -Dashboard tabs in IBM Process Portal
    -Services run from the launch tab in Process Portal
    -Admin services in the Process Admin Console
    -A URL service directly run from a URL, for example
       /teamworks/executeServiceByName?
       processApp=HSS&serviceName=MyService
    
    You might notice that this issue does not occur if the service
    was the last object modified for the process app. Making changes
    to anything else triggers the issue again.
    
    
       This error is also logged
    [1/18/16 12:12:30:721 ART] 00000138 EJBWorkflowMa E
    CWLLG0594E: An
    exception occurred while initializing the runnable thread.
    Error:
    com.lombardisoftware.component.common.workflow.WorkflowProcessIt
    emException: java.util.ConcurrentModificationException
    
    com.lombardisoftware.component.common.workflow.WorkflowProcessIt
    emException: java.util.ConcurrentModificationException
     at
    com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
    b(ExecutionJob.java:478)
     at
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
    doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1432)
     at
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
    resumeProcess(EJBWorkflowManagerBean.java:413)
     at
    com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWor
    kflowManager_82478d70.resumeProcess(Unknown Source)
     at
    com.lombardisoftware.server.ejb.workflow._EJBWorkflowManagerInte
    rface_St
    ub.resumeProcess(_EJBWorkflowManagerInterface_Stub.java:518)
    ...
    Caused by: java.util.ConcurrentModificationException
     at
    java.util.LinkedHashMap$AbstractMapIterator.checkConcurrentMod(L
    inkedHashMap.java:136)
     at
    java.util.LinkedHashMap$AbstractMapIterator.makeNext(LinkedHashM
    ap.java:141)
     at
    java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:201)
     at
    com.lombardisoftware.server.core.ManagedAssetClassLoader.toStrin
    g(ManagedAssetClassLoader.java:196)
     at java.lang.String.valueOf(String.java:1569)
     at java.lang.StringBuilder.append(StringBuilder.java:194)
     at
    com.lombardisoftware.server.core.ManagedAssetClassLoaderUtil.exe
    cuteWith
    ManagedAssetClassLoader(ManagedAssetClassLoaderUtil.java:44)
     at
    teamworks.connector.JavaReflectionConnector.execute(JavaReflecti
    onConnector.java:56)
     at
    com.lombardisoftware.component.javaconnector.worker.JavaConnecto
    rWorker.invokeJavaMethod(JavaConnectorWorker.java:153)
     at
    com.lombardisoftware.component.javaconnector.worker.JavaConnecto
    rWorker.doJob(JavaConnectorWorker.java:86)
     at
    com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
    b(ExecutionJob.java:461)
     ... 85 more
    

Local fix

Problem summary

  • This issue occurs because the permissions to run the service in
    the context of a Tip snapshot are not checked correctly.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.6.0 Cumulative Fix 2 (CF02)
    that corrects the permission check for services started in the
    context of a Tip snapshot.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR55136:
    
    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 JR55136, 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

    JR55136

  • 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-02-02

  • Closed date

    2016-02-18

  • Last modified date

    2016-12-19

  • 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

[{"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:
19 December 2016