PK86523: SLOW RUNNING OF MODULE UPDATE OPERATION.

Fixes are available

APAR status

Closed as program error.

Error description

Single module operations can erroneously attempt to scan the
contents of the system configured temporary directory.  This
occurs because of a lookup of the library classpath of the
parent application of the module, which erroneously opens the
parent directory of the module as an application.  The result is
a performance problem, and possibly an incorrect determination
of the library classpath.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: A sevenfold increase is seen in the     *
*                      time needed to update a Java J2EE       *
*                      Application module.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The symptom on this problem is an increase (by 100% or more) in
the time which is required to perform a module update, and, a
java core showing a large amount of time being spent beneath a
call to ArchiveImpl.getLibraryDirectoryClassPath, and showing
a call from ArchiveImpl.getLibraryDirectoryClassPath to
CommonarchiveFactoryImpl.openEARFile.

For example:

3XMTHREADINFO      "Thread-42" TID:0x1691FD00,
j9thread_t:0x150BBC28, state:R, prio=5
3XMTHREADINFO1            (native thread ID:0x1534, native
priority:0x5, native policy:UNKNOWN)
4XESTACKTRACE          at java/io/WinNTFileSystem.list(Native
Method)
4XESTACKTRACE          at
java/io/File.list(File.java:985(Compiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/Directo
ryLoadStrategyImpl.addFiles(DirectoryLoadStrategyImpl.java:591(C
ompiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/Directo
ryLoadStrategyImpl.addFiles(DirectoryLoadStrategyImpl.java:583(C
ompiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/Directo
ryLoadStrategyImpl.getFiles(DirectoryLoadStrategyImpl.java:711)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/LoadStr
ategyImpl.collectFiles(LoadStrategyImpl.java:666(Compiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/ContainerIm
pl.getFiles(ContainerImpl.java:298(Compiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/Ear50No
DDImportStrategyImpl.loadDeploymentDescriptor(Ear50NoDDImportStr
ategyImpl.java:438(Compiled Code))
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/strategy/Ear50No
DDImportStrategyImpl.importMetaData(Ear50NoDDImportStrategyImpl.
java:253)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/EARFileImpl
.getDeploymentDescriptor(EARFileImpl.java:377(Compiled Code))
4XESTACKTRACE          at
com/ibm/etools/commonarchive/impl/EARFileImpl.initializeModuleEx
tensions(EARFileImpl.java:641)
4XESTACKTRACE          at
com/ibm/etools/commonarchive/impl/EARFileImpl.initializeAfterOpe
n(EARFileImpl.java:720)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/Commonarchi
veFactoryImpl.openSpecificArchive(CommonarchiveFactoryImpl.java:
1517)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/Commonarchi
veFactoryImpl.openEARFile(CommonarchiveFactoryImpl.java:1245)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/ArchiveImpl
.getLibraryDirectoryClassPath(ArchiveImpl.java:2763)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/ArchiveImpl
.getClassPathClassLoader(ArchiveImpl.java:1232)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/ArchiveImpl
.initializeClassLoader(ArchiveImpl.java:1771)
4XESTACKTRACE          at
org/eclipse/jst/j2ee/commonarchivecore/internal/impl/ArchiveImpl
.getArchiveClassLoader(ArchiveImpl.java:1194)
4XESTACKTRACE          at
com/ibm/ws/websvcs/desc/WSModuleDescriptorImpl.initializeClassLo
ader(WSModuleDescriptorImpl.java:1457)
4XESTACKTRACE          at
com/ibm/ws/websvcs/desc/WSModuleDescriptorImpl.<init>(WSModuleDe
scriptorImpl.java:303)
4XESTACKTRACE          at
com/ibm/ws/websvcs/desc/WSDescriptionBuilderImpl.getModuleDescri
ptor(WSDescriptionBuilderImpl.java:51)
4XESTACKTRACE          at
com/ibm/ws/websvcs/desc/WSDescriptionBuilderImpl.getModuleDescri
ptor(WSDescriptionBuilderImpl.java:40)
4XESTACKTRACE          at
com/ibm/ws/webservices/admin/utils/CommonUtils.hasWebServices(Co
mmonUtils.java:294)
4XESTACKTRACE          at
com/ibm/ws/webservices/admin/utils/CommonUtils.hasJAXWSWebServic
es(CommonUtils.java:236)
4XESTACKTRACE          at
com/ibm/ws/webservices/admin/deploy/DeploymentValidation.validat
e(DeploymentValidation.java:517)
4XESTACKTRACE          at
com/ibm/ws/webservices/admin/deploy/DeploymentValidation.validat
e(DeploymentValidation.java:493)
4XESTACKTRACE          at
com/ibm/ws/webservices/admin/deploy/DeploymentValidation.validat
eOperation_Required(DeploymentValidation.java:202)
4XESTACKTRACE          at
com/ibm/ws/management/application/task/ValidateAppTask.performTa
sk(ValidateAppTask.java:265)
4XESTACKTRACE          at
com/ibm/ws/management/application/SchedulerImpl.run(SchedulerImp
l.java:284)
4XESTACKTRACE          at java/lang/Thread.run(Thread.java:735)

Problem conclusion

The problem occurs because of an erroneous call to open the
parent directory of the target module as a Java Enterprise
application.  In the best case, this cases a single extra step
which opens the target module.  In other cases, the target
module is in a directory with many other unrelated java
resources, for example, java archive files, and the extra step
erroneously opens the parent directory as a java enterprise
application with the java archive files as modules.  In this
second case, the time to update the module can see an
arbitrary increase.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5 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
PK86523
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-13
Closed date
2009-05-27
Last modified date
2009-05-27

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 APP S
Fixed component ID
5724J0800

Applicable component levels

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK86523: SLOW RUNNING OF MODULE UPDATE OPERATION.

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

R700 PSY

Document Information

Share your feedback

Need support?