IBM Support

PM76486: NAME SERVER CODE NEEDS TO BE OPTIMIZED WHEN A CONFIG CHANGE IS MADE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Starting in v8.0, the name server must read app deployment data
    (deployment.xml) for each application for runtime use.  It
    keeps its in-memory cache up-to-date by listening to config
    change events.  When a config change occurs, it it re-reads all
    app data.  The code needs to be optimized to read config data
    only for applications that have changed instead of for all of
    them.
    
    If there are lots of applications, you can see these messages
    in the control region joblog:
    
    Trace: 2012/10/04 10:53:13.623 02 t=7C14C0 c=UNK key=S2 tag=
    (13007004)
    SourceId: com.ibm.ejs.util.am.AlarmThreadMonitor
    ExtendedMessage: BBOO0221W: UTLS0008W: The return of alarm
    thread "Non-deferrable Alarm : 3" (00000013) to the alarm
    thread pool has been delayed for 15582 milliseconds. This may
    be preventing normal alarm function within the application
    server. The alarm listener stack trace is as follows:
    at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
    at java.io.UnixFileSystem.
        getBooleanAttributes(UnixFileSystem.java:239)
    at java.io.File.isDirectory(File.java:765)
    at sun.net.www.protocol.file.FileURLConnection.
        connect(FileURLConnection.java:77)
    at sun.net.www.protocol.file.FileURLConnection.
        getInputStream(FileURLConnection.java:173)
    at org.apache.xerces.impl.XMLEntityManager.
        setupCurrentEntity(Unknown Source)
    at org.apache.xerces.impl.XMLVersionDetector.
       determineDocVersion(Unknown Source)
    at org.apache.xerces.parsers.
       .parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.
        parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.
        parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.
        parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at com.ibm.ws.runtime.config.ConfigDocumentImpl.
        load(ConfigDocumentImpl.java:200)
    at com.ibm.ws.runtime.config.ConfigServiceImpl.
        getDocument(ConfigServiceImpl.java:182)
    at com.ibm.ws.runtime.config.ConfigServiceImpl.
        getDocumentObjects(ConfigServiceImpl.java:126)
    at com.ibm.ws.runtime.config.ConfigServiceImpl.
        getDocumentObjects(ConfigServiceImpl.java:120)
    at com.ibm.ws.naming.bootstrap.AppConfigInfoBuilder.
        collectAppDataFromDeployments(AppConfigInfoBuilder.java:230)
    at com.ibm.ws.naming.bootstrap.ConfigInfoBuilder.
        initApplicationInfo(ConfigInfoBuilder.java:1058)
    at com.ibm.ws.naming.bootstrap.ConfigInfoBuilder.
        buildConfigInfo(ConfigInfoBuilder.java:274)
    at com.ibm.ws.naming.bootstrap.NameServerImpl$2.
        run(NameServerImpl.java:994)
    at com.ibm.ws.security.auth.ContextManagerImpl.
        runAs(ContextManagerImpl.java:5405)
    at com.ibm.ws.security.auth.ContextManagerImpl.
        runAsSystem(ContextManagerImpl.java:5531)
    at com.ibm.ws.security.core.SecurityContext.
        runAsSystem(SecurityContext.java:255)
    at com.ibm.ws.naming.bootstrap.NameServerImpl.
         createConfigDiff(NameServerImpl.java:998)
    at com.ibm.ws.naming.bootstrap.NameServerImpl.
         access$1200(NameServerImpl.java:208)
    at com.ibm.ws.naming.bootstrap.NameServerImpl$Listener.
         configChanged(NameServerImpl.java:1433)
    at com.ibm.ws.management.component.
         ConfigChangeHandler$ConfigChangeEventDispatcher.
         run(ConfigChangeHandler.java:365)
    at com.ibm.ws.management.component.ConfigChangeHandler.
         alarm(ConfigChangeHandler.java:167)
    at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:127)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650).
    
    Trace: 2012/10/04 10:53:38.660 02 t=7BF0B8 c=UNK key=S2 tag=
    (13007004)
    SourceId: com.ibm.ejs.util.am.AlarmThreadMonitor
    ExtendedMessage: BBOO0221W: UTLS0009W: Alarm Thread
    "Non-deferrable Alarm : 3" (00000013) previously reported to be
    delayed has now completed.  It was active for approximately
    40624 milliseconds.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Saving configuration changes            *
    *                      take an excessive amount of time if     *
    *                      many applications are installed.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Saving configuration changes take an excessive amount of time
    if many applications are installed.
    An error message similar to the following message might be
    found in SystemOut.log:  UTLS0008W: The return of alarm thread
    "Non-deferrable Alarm : 0"  (00000004) to the alarm thread
    pool has been delayed for 14935 milliseconds. This may be
    preventing normal alarm function within the application server.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM76486

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-05

  • Closed date

    2013-01-11

  • Last modified date

    2013-01-11

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021