IBM Support

JR62930: THE IBM BPM EVENT EMITTER DOESN'T USE THE EVENTS FROM THE QUEUE THAT THIS EMITTER LISTENS TO

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

  • When there are several deployment environments in the cell, all
    the emitters use the events from the same queue and not from the
     queue specific to each emitter.
    
    Every emitter message-driven bean (MDB) binding wrongly refers
    to the same queue and activation specification.
    

Local fix

Problem summary

  • THE IBM BPM EVENT EMITTER DOESN'T USE THE EVENTS FROM THE QUEUE
    THAT THIS EMITTER LISTENS TO.
    

Problem conclusion

  • A fix is available or will be available that ensures the IBM BPM
     event emitter uses the events from the right queue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62930

  • 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-10-30

  • Closed date

    2020-10-30

  • Last modified date

    2020-10-30

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0.1"}]

Document Information

Modified date:
14 December 2020