IBM Support

PM09376: SAVE CONFIGURATION ENCOUNTERS HTTP 500 EXCEPTION IN THE ADMINISTRATIVE CONSOLE

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using the 7.0.0.7 console; WebSphere Application Server
    administrative users experience the "HTTP 500" Error displayed
    in the administrative console after any configuration changes
    in the console.
    
    The system out contains the message
    
    E com.ibm.ws.webcontainer.servlet.ServletWrapper service
    SRVE0068E:
    Uncaught exception created in one of the service methods of the
    servlet
    action in application isclite. Exception created :
    javax.servlet.ServletException: java.util.NoSuchElementException
    at
    org.apache.struts.action.RequestProcessor.processException(Unkno
    wn
    Source)
    at
    org.apache.struts.action.RequestProcessor.processActionPerform(U
    nknown
    Source)
    at org.apache.struts.action.RequestProcessor.process(Unknown
    Source)
    at org.apache.struts.action.ActionServlet.process(Unknown
    Source)
    at org.apache.struts.action.ActionServlet.doGet(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at
    com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
    apper.ja
    va:1583)
    

Local fix

  • Deleting the preferences.xml file completely would cause
    another code
    path to run. The console code assumes that you wanted to start
    over with
    a clean prefs, and so it makes a call to remove the preferences
    node
    from the current preferences implementation.This
    removes the
    preferences node that was stored in the windows registry.
    When the file is re-built from scratch, it does not contain the
    syncWithNodes key. Since the Windows registry also does not
    contain the
    key, there is no alternate value to pick up, and so the problem
    does not reappear.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server 7.0 using the Administrative Console *
    ****************************************************************
    * PROBLEM DESCRIPTION: NoSuchElementException while in the     *
    *                      Administrative Console Save operation   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a save operation is performed in a stand alone
    application server console, a NoSuchElementException is
    displayed on the screen.
    
    This is observed on Microsoft Windows operating systems, when
    multiple profiles are exist on the machine. A DMGR profile has
    a "Synchronize changes with Nodes" option in the Console
    Preferences. On Microsoft Windows, the Console Preferences
    could be saved at the Microsoft Windows registry. When a stand
    alone application server is later used, it incorrectly picks
    up the previous DMGR's Console Preferences settings from the
    registry. This causes a problem because the "Synchronize
    changes with Nodes" is not applicable to stand alone
    application server.
    

Problem conclusion

Temporary fix

  • Deleting the <profile>/consolepreferences/<user name hash>
    preferences.xml file completely would cause another code path
    to run. The console code assumes that you wanted to start over
    with a clean prefs, and so it makes a call to remove the
    preferences node from the current preferences
    implementation. This removes the preferences node
    that was stored in the Microsoft Windows registry. When the
    file is re-built from scratch, it does not contain the
    syncWithNodes key. Since the Microsoft Windows registry also
    does not contain the key, there is no alternate value to pick
    up, and so the problem does not reappear.
    

Comments

APAR Information

  • APAR number

    PM09376

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-08

  • Closed date

    2010-06-04

  • Last modified date

    2010-06-04

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM09376

Modified date: 04 June 2010