IBM Support

PM15106: PORTAL SERVER UPGRADES FAILING ON UNIX PLATFORMS AIX AND LINUX WITH EXCEPTIONININITIALIZERERROR.

Fixes are available

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
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
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • Portal Server V610X upgrade failing on Unix operating systems
    AIX and Linux. The extension registry cache files are not
    being updated after a Portal V610X product upgrade. This causes
    the older cache to load, leading to the ExtensionPoint not
    found error.
    .
    [30/10/09 13:09:30:456 GMT] 00000015 ExtensionsLoo E
    
    com.ibm.wps.services.extreg.ExtensionsLookupContext lookup
    (Name)
    NamingException catched:ExtensionPoint not found:
    com.ibm.wps.ai.base.api.service.ServiceLocator. Please turn on
    the
    traces for 'com.ibm.wps.services.extreg.*=all' to see the full
    stacktrace.
    [30/10/09 13:09:30:459 GMT] 00000015 Servlet       E
    com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of
    service failed.
    
    java.lang.ExceptionInInitializerError
    .
    The root cause of the problem is the extension registry is not
    able to get the last modified time of the jar files, and thus
    does not reload them. In the logs, URLConnection.getLastModified
    () is always returning 0.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V6.1       *
    *                  and V7.0 users upgrading IBM WebSphere      *
    *                  Portal Server                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When upgrading WebSphere Portal         *
    *                      Server, an ExtensionPoint not found     *
    *                      error is seen, and upgrade fails to     *
    *                      complete.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When upgrading WebSphere Portal Server, the following error is
    seen in the logs during the upgrade:
    [30/10/09 13:09:30:456 GMT] 00000015 ExtensionsLoo E
    com.ibm.wps.services.extreg.ExtensionsLookupContext lookup
    (Name)
    NamingException catched:ExtensionPoint not found:
    com.ibm.wps.ai.base.api.service.ServiceLocator. Please turn on
    the traces for 'com.ibm.wps.services.extreg.*=all' to see the
    full stacktrace.
    [30/10/09 13:09:30:459 GMT] 00000015 Servlet       E
    com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of
    service failed.
    
    java.lang.ExceptionInInitializerError
    

Problem conclusion

  • The root cause of the problem is the extension registry is not
    able to get the last modified time of the jar files, and thus
    does not reload them. A code change was made to get the file
    timestamps an alternate way.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.33 and 7.0.0.13.  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

    PM15106

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-24

  • Closed date

    2010-07-13

  • Last modified date

    2010-07-13

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM15106

Modified date: 13 July 2010