IBM Support

PI29210: MANAGEDSERVICEFACTORYTRACKER/BUNDLECONTEXTIMPL THROW ILLEGALSTAT EEXCEPTION WHEN SERVER IS BEING STOPPED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While server is being stopped, the following message is
    written to the log file:
    
    Exception = java.lang.IllegalStateException
    Source =
    com.ibm.ws.config.admin.internal.ManagedServiceFactoryTracke
    r
    probeid = asyncUpdated()
    Stack Dump = java.lang.IllegalStateException: BundleContext
    is no longer valid
    at
    org.eclipse.osgi.internal.framework.BundleContextImpl.checkV
    alid(BundleContextImpl.java:983)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: ManagedServiceFactoryTracker/BundleCont *
    *                      extImpl throw IllegalStateException     *
    *                      when server is being stopped            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While server is being stopped, the following message is written
    to the log file:
    
    Exception = java.lang.IllegalStateException
    Source =
    com.ibm.ws.config.admin.internal.ManagedServiceFactoryTracker
    probeid = asyncUpdated()
    Stack Dump = java.lang.IllegalStateException: BundleContext is
    no longer valid
    at
    org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid
    (BundleContextImpl.java:983)
    

Problem conclusion

  • This exception arose while a server was in the process of being
    stopped, and was reporting that data structures were being shut
    down. That was actually an expected exception, and was being
    handled correctly... but was being logged as well. We have
    corrected the code to process this silently.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.5.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • This message is annoying, but harmless. Users can ignore it
    until they are ready to apply the APAR.
    

Comments

APAR Information

  • APAR number

    PI29210

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-07

  • Closed date

    2015-02-16

  • Last modified date

    2015-02-16

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022