IBM Support

JR46360: EVENT SEQUENCING IS NOT STARTING CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During server start up, Event sequencing is not able to load up
    certain artifacts and hence does not start properly. This in
    turn effects modules using event sequencing and these modules do
    not function correctly. The error seen is as below in FFDC.
    
    
    java.lang.NullPointerException    at
    com.ibm.ws.al.scope.ALScopeImpl$1.run(ALScopeImpl.java:250)
    at
    com.ibm.ws.al.scope.ALScopeImpl$1.run(ALScopeImpl.java:248)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:229)
      at
    com.ibm.ws.al.scope.ALScopeImpl.getCatalog(ALScopeImpl.java:248)
    at
    com.ibm.ws.al.scope.ScopeContextImpl.getCatalog(ScopeContextImpl
    .java:14
    3)    at
    com.ibm.ws.al.ScopeContextAdapter.queryURLs(ScopeContextAdapter.
    java:141
    )    at
    com.ibm.ws.al.ArtifactLoaderAdapter.queryURLs(ArtifactLoaderAdap
    ter.java
    :83)    at
    com.ibm.ws.monitoring.utils.ModelLocator.locateArtifactByAL(Mode
    lLocator
    .java:146)    at
    com.ibm.ws.monitoring.core.EventNatures.getEventNaturesForCompon
    entType(
    EventNatures.java:124)    at
    com.ibm.ws.monitoring.core.MonitorFactory.load(MonitorFactory.ja
    va:81)
      at
    com.ibm.ws.monitoring.core.MonitorFactory.create(MonitorFactory.
    java:54)
        at
    
    The error thrown in SystemOut.log during server start up is:
    
    [3/26/13 10:57:19:775 CDT] 0000003b               E
    com.ibm.ws.monitoring.core.MonitorFactory load() CWLBS0055E:
    Cannot load
    event specification of {0}. Mock event source context will be
    returned
    instead.
    
    java.lang.IllegalArgumentException:
    event definition file (xsd) can't be loaded by
    tns:{http://www.ibm.com/xmlns/prod/websphere/fe/7.0.0}StoreAndFo
    rward
     at
    com.ibm.ws.monitoring.core.EventNatures.getEventNaturesForCompon
    entType(
    EventNatures.java:138)
     at
    com.ibm.ws.monitoring.core.MonitorFactory.load(MonitorFactory.ja
    va:81)
     at
    com.ibm.ws.monitoring.core.MonitorFactory.create(MonitorFactory.
    java:54)
     at
    com.ibm.wbiserver.storeandfwd.service.StoreAndForwardStateManage
    r.<clini
    t>(StoreAndForwardStateManager.java:61)
     at java.lang.J9VMInternals.initializeImpl(Native Method)
     at java.lang.J9VMInternals.initialize(J9VMInternals.java:228)
     at
    com.ibm.wbiserver.sequencing.service.messaging.ESAsyncConsumerCa
    llBackIm
    pl.start(ESAsyncConsumerCallBackImpl.java:183)
     at
    com.ibm.wbiserver.sequencing.service.AppEsService.start(AppEsSer
    vice.jav
    a:77)
     at
    com.ibm.wbiserver.sequencing.service.BaseEsService.startESServic
    es(BaseE
    sService.java:251)
     at
    com.ibm.wbiserver.sequencing.service.messaging.EsMeConnectionSer
    vice.run
    (EsMeConnectionService.java:217)
     at java.lang.Thread.run(Thread.java:772)
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Business Process Manager 8.0 users          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Event sequencing is not started         *
    *                      correctly                               *
    *                      during server starting.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During server start up, Event sequencing is not able to load up
    certain artifacts and hence does not start properly. This in
    turn effects modules using event sequencing and these modules
    do
    not function correctly. The log and ffdc could show
    IllegalArgumentException or NullPointerException.
    

Problem conclusion

  • This defect is resolved by correcting the event sequencing
    classloader.
    
    Install/Dependency information is available in the readme.txt on
    FixCentral. When the user goes to the download files page
    in FixCentral, the readme will be available with the fix package
    as a separate download.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR46360

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-16

  • Closed date

    2013-07-10

  • Last modified date

    2013-07-10

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

  • Fixed component ID

    5725C9400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 January 2022