IBM Support

JR43721: UNDER HEAVY LOAD SITUATIONS AN UNEXPECTEDFAILUREEXCEPTION MAY OCCUR

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.

 

APAR status

  • Closed as program error.

Error description

  • Under heavy load situations, when workmanager based navigation
    is used, the followimg exception can be seen in SystemOut.log:
    
    com.ibm.bpe.api.UnexpectedFailureException: CWWBA0010E:
    com.ibm.bpe.util.ProcessAssertionError: Precondition violation
    !(pkid !=null) in method >>
    
    com.ibm.bpe.database.Tom.getSavedEngineMessageB(Tom.java:14716)
     at com.ibm.bpe.util.Assert.precondition(Assert.java:145)
     at com.ibm.bpe.database.Tom.getSavedEngineMessageB
      (Tom.java:14716)
     at com.ibm.bpe.framework.navigation.NavigationMessageHandler.
      handleSingleMessage(NavigationMesssageHandler.java:357)
    at com.ibm.bpe.framework.navigation.NavigationMessageHandler.
      sendInternalMessage(NavigationMessageHandler.java:176)
    at com.ibm.bpe.framework.ProcessJMSQueueManager.
      sendInternalMessage(ProcessJMSQueueManager.java:216)
    ...
    

Local fix

Problem summary

  • The problem occurs when
    - BPC is configred to use work manager based navigation (WMBN)
    - the load is that high that WMBN's internal message pool cannot
    hold all navigation messages that are produced
    In this situation, BPC does not put messages into WMBNs message
    pool, but sends them directly to the bpeIntQueue via JMS.
    In addition it tries to mark the database record backing these
    messages with the info that the message has already been
    sent to JMS. Unfortunately, at this point in time the database
    record does not exist and this causes the error.
    

Problem conclusion

  • The fix checks for existence of the database record before
    attempting to update it.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR43721

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-09

  • Closed date

    2015-02-06

  • Last modified date

    2015-02-06

  • APAR is sysrouted FROM one or more of the following:

    JR43712

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 February 2015