IBM Support

JR63040: THE EXECUTION OF HISTORICAL DATA PLAYBACK FAILS ON A THREE-CLUSTER TOPOLOGY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • On a three-cluster environment, running the Historical Data
    Playback REST API fails with the following exception:
    
    
    ExceptionChec I   WARNING: Exception not recognized by
    com.ibm.bpmstd.engine.ops.api.rest.impl.ExceptionChecker.
    Exception associated with method
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper.invokeHistoricalDataPlayback().
    Exception message is: An error occurred while processing events
    for the process instance '0'.
    
    com.lombardisoftware.core.TeamWorksException: An error occurred
    while processing events for the process instance '0'.
    at
    com.ibm.bpm.bui.emitter.DataExtractor.extractRawEvents(DataExtra
    ctor.java:337)
    at
    com.ibm.bpm.bui.emitter.HistoricalDataPlayback.playback(Historic
    alDataPlayback.java:126)
    at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper.invokeHistoricalDataPlayback(StdHistoricalDataPlaybackHe
    lper.java:83)
    at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper.access$000(StdHistoricalDataPlaybackHelper.java:39)
    at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper$1.call(StdHistoricalDataPlaybackHelper.java:179)
    at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper$1.call(StdHistoricalDataPlaybackHelper.java:176)
    at
    com.ibm.bpmstd.engine.api.rest.util.AsyncHelper$1.run(AsyncHelpe
    r.java:156)
    at
    com.ibm.bpm.util.WASAsynchInvocationImpl$1.run(WASAsynchInvocati
    onImpl.java:37)
    at
    com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java
    :271)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:678)
    at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
    at
    com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE
    xecutionContextImpl.java:222)
    at
    com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:20
    6)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    Caused by: java.lang.RuntimeException:
    java.io.FileNotFoundException: /config/BPMEventEmitter.yml (No
    such file or directory)
    at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:81)
    at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:70)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:734)
    at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl.getConfigurationFil
    e(BPMAnalyticsConfigImpl.java:70)
    at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.getEmitterConfiguration
    (EmitterUtil.java:62)
    at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.getConfigProperty(Emitt
    erUtil.java:83)
    at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.isBpmEmitterEnabled(Emi
    tterUtil.java:45)
    at
    com.ibm.bpm.bui.emitter.database.BpmDAO.isBpmEmitterEnabled(BpmD
    AO.java:368)
    at
    com.ibm.bpm.bui.emitter.DataExtractor.extractRawEvents(DataExtra
    ctor.java:186)
    ... 13 more
    Caused by: java.io.FileNotFoundException:
    /config/BPMEventEmitter.yml (No such file or directory)
    at java.io.FileInputStream.open0(Native Method)
    at java.io.FileInputStream.open(FileInputStream.java:212)
    at java.io.FileInputStream.(FileInputStream.java:152)
    at java.io.FileInputStream.(FileInputStream.java:104)
    at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:78)
    ... 21 more
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
     at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper.invokeHistoricalDataPlayback(StdHistoricalDataPlaybackHe
    lper.java:83)
     at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper.access$000(StdHistoricalDataPlaybackHelper.java:39)
     at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper$1.call(StdHistoricalDataPlaybackHelper.java:179)
     at
    com.ibm.bpmstd.engine.ops.api.rest.util.StdHistoricalDataPlaybac
    kHelper$1.call(StdHistoricalDataPlaybackHelper.java:176)
     at
    com.ibm.bpmstd.engine.api.rest.util.AsyncHelper$1.run(AsyncHelpe
    r.java:156)
     at
    com.ibm.bpm.util.WASAsynchInvocationImpl$1.run(WASAsynchInvocati
    onImpl.java:37)
     at
    com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java
    :271)
     at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:678)
     at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
     at
    com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE
    xecutionContextImpl.java:222)
     at
    com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:20
    6)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    Caused by: java.lang.RuntimeException:
    java.io.FileNotFoundException: /config/BPMEventEmitter.yml (No
    such file or directory)
     at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:81)
     at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:70)
     at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:734)
     at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl.getConfigurationFil
    e(BPMAnalyticsConfigImpl.java:70)
     at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.getEmitterConfiguration
    (EmitterUtil.java:62)
     at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.getConfigProperty(Emitt
    erUtil.java:83)
     at
    com.ibm.bpm.bui.emitter.util.EmitterUtil.isBpmEmitterEnabled(Emi
    tterUtil.java:45)
     at
    com.ibm.bpm.bui.emitter.database.BpmDAO.isBpmEmitterEnabled(BpmD
    AO.java:368)
     at
    com.ibm.bpm.bui.emitter.DataExtractor.extractRawEvents(DataExtra
    ctor.java:186)
     ... 13 more
    Caused by: java.io.FileNotFoundException:
    /config/BPMEventEmitter.yml (No such file or directory)
     at java.io.FileInputStream.open0(Native Method)
     at java.io.FileInputStream.open(FileInputStream.java:212)
     at java.io.FileInputStream.(FileInputStream.java:152)
     at java.io.FileInputStream.(FileInputStream.java:104)
     at
    com.ibm.bpm.oi.config.BPMAnalyticsConfigImpl$2.run(BPMAnalyticsC
    onfigImpl.java:78)
     ... 21 more
    

Local fix

Problem summary

  • RUNNING A HISTORICAL DATA PLAYBACK REST API FAILS ON A
    THREE-CLUSTER TOPOLOGY
    

Problem conclusion

  • A fix is available or will be available that ensures the
    Historical Data Playback doesn't fail when running on a
    three-cluster topology.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR63040

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    J00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-26

  • Closed date

    2021-02-02

  • Last modified date

    2021-02-02

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0.1"}]

Document Information

Modified date:
21 June 2021