IBM Support

PM50224: CHANGING EJB TIMER SERVICE SETTINGS AFTER MIGRATION V8.0 RESULTS IN NMSV0800W DUE TO FEATURENOTFOUNDEXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After deploying a WebSphere AppServer 6.1 application under the
    WebSphere Deployment Manager 8.0, when attempting to change the
    EJB Container's EJB Timer Service settings using the WebSphere
    Deployment Manager 8.0 administrative console, the following
    exception is logged when trying to restart the WebSphere
    Application Server 6.1 server.
    .
    NMSV0800W: Exception encountered loading configuration file
    "server.xml".
    org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
    'uniqueTimerManagerForNP' not found. (file:
    <file path> ).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  version 8.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a mixed cell environment, you        *
    *                      cannot restart a pre version 8          *
    *                      server after using a version 8          *
    *                      deployment manager to edit the          *
    *                      Enterprise JavaBean (EJB) timer         *
    *                      settings for the server.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a mixed cell environment, you cannot restart a pre version 8
    server after using a version 8 deployment manager to edit the
    Enterprise JavaBean (EJB) timer settings for the server. After
    editing the EJB timer settings, the attribute,
    uniqueTimerManagerForNP, is added to the server.xml file on
    the pre version 8 server. The pre version 8 server does not
    know about this new attribute and during an attempt to restart
    the server, it cannot start back up. It fails with an
    exception similar to the following:
    NMSV0800W: Exception encountered loading configuration file
    "server.xml".
    org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
    'uniqueTimerManagerForNP' not found.
    

Problem conclusion

  • The code has been fixed to not add the attribute,
    uniqueTimerManagerForNP, to pre version 8 servers.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 8.0.0.3. Please refer to the Recommended Updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM50224

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-17

  • Closed date

    2012-01-05

  • Last modified date

    2012-10-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
28 October 2021