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

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?