IBM Support

IT28965: ISSUES WHEN STOPPING PERFORMANCE STATISTICS WHILE HANDLING PROCESS DATA

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

  • While stopping PerformanceStats noticed that BPs did not
    complete successfully but went to the following states:
    
    3 Business Process on Halted state
    
    1 Business Process on Waiting state
    
    1 Business Process on Interrupted_Man state
    
    
    In the system.log file, there are many meesages starting a (the
    time when PerformanceStats was stopped) like the following ones:
    
    
    
    [2019-04-04 11:57:05.642] ERROR stop perf logger for sterling
    logger failed id=XPathHelper.executeXPath type=ENGINE
    
    [2019-04-04 11:57:05.642] ERROR stop perf logger for yantra
    logger failed id=XPathHelper.executeXPath type=ENGINE
    
    [2019-04-04 11:57:19.223] ERROR This perf logger for
    id=CONTIUE_OWFC type=WORKFLOW hasn't been started yet
    
    [2019-04-04 11:57:47.578] ERROR stop perf logger for sterling
    logger failed id=BPIndex.processData type=USERDEFINED
    
    [2019-04-04 11:57:47.578] ERROR stop perf logger for yantra
    logger failed id=BPIndex.processData type=USERDEFINED
    
    
    
    
    Errors indicating that there are issues with processing BPs
    start later (see e.g. wf.log):
    
    
    [2019-04-04 12:00:51.47] ERROR 000110070158
    WORKFLOW.ACTIVITY_ENGINE.ERR_ActivityEngineHelper_invokeService2
    1 ActivityEngineHelper.invokeService() caught exception while
    attempting to execute service LightweightJDBCAdapterQuery
    
    [2019-04-04 12:00:51.47] ERRORDTL
    [1554372051470]java.lang.NullPointerException
    
    
    
    It looks like when searching for eligible adapters that belong
    to a group SI checks if the adapter is enabled and then makes
    decision based on node load, but doesn't check mandatory node
    restriction.
    

Local fix

  • RTC: 582404
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    Many issues occur when stopping performance statistics during
    handling of performance data.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    
    A code fix is provided.
    
    
    
    The reason for the exception seems to happen when the
    
    Performance logger is trying to flush the performance data and
    the flush instance pointer seems to be null.
    
    
    And exception in logs were showing the same:
    
    ERRORDTL [1554372051469]java.lang.NullPointerException
    
        at
    com.sterlingcommerce.woodstock.test.performance.PerformanceLogge
    r.addToLogs(PerformanceLogger.java:906)
    
        at
    com.sterlingcommerce.woodstock.test.performance.PerformanceLogge
    r.stopSterlingLogging(PerformanceLogger.java:874)
    
        at
    com.sterlingcommerce.woodstock.test.performance.PerformanceLogge
    r.stopLogging(PerformanceLogger.java:703)
    
        at
    com.sterlingcommerce.woodstock.test.performance.PerfLoggingExten
    sion.stopLogging(PerfLoggingExtension.java:47)
    
        at
    com.sterlingcommerce.woodstock.util.frame.SimplePerfLogger.stopL
    ogging(SimplePerfLogger.java:26)
    
        at
    com.sterlingcommerce.woodstock.workflow.BaseDocument.persist(Bas
    eDocument.java:2855)
    
        at
    com.sterlingcommerce.woodstock.workflow.Document.persistDoc(Docu
    ment.java:1052)
    
        at
    com.sterlingcommerce.woodstock.workflow.Document.persist(Documen
    t.java:1005)
    
        at
    com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(
    WorkFlowContext.java:5058)
    
        at
    com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(
    WorkFlowContext.java:4367)
    
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.persistWfc(ActivityEngineHelper.java:3246)
    
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.postInvokePostNextNodeProcessing(ActivityEngineHelp
    er.java:2344)
    
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.postInvokeService(ActivityEngineHelper.java:2206)
    
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.nextMainLogic(ActivityEngineHelper.java:656)
    
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.next(ActivityEngineHelper.java:362)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.doWork(WorkFlowQueueListener.java:461)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.run(WorkFlowQueueListener.java:240)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.onMessage(WorkFlowQueueListener.java:197)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.onMessage(WorkFlowQueueListener.java:184)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(
    wfTransporter.java:444)
    
        at
    com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Work
    er.run(BasicExecutor.java:529)
    
        at java.lang.Thread.run(Thread.java:798)
    
    
    It is due to issue with synchronisation while flushing the log
    content. Made code changes to solve the synchronisation issue.
    
    
    Delivered In:
    5020603_11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28965

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    525

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-07

  • Closed date

    2019-08-30

  • Last modified date

    2019-09-06

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.5","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
06 September 2019