APAR status
Closed as program error.
Error description
When a node is federated to DMgr, AppServer uses filename,
displayname to build its wstemp, config and installedApps
directory structure.
If Filename and/or DisplayName is already long (~25 chars or
above) it will lead to Path Name limit excess on Windows.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server V5.x users *
* who deploy applications with very long names *
* on Windows. *
****************************************************************
* PROBLEM DESCRIPTION: Most Windows OS have a file path limit *
* of 259 characters (XP allows longer *
* paths). When an application is *
* deployed with a long name, it is *
* possible the deployed application *
* files will reach this path limit. *
* Currently, there is no check performed *
* and the error messages when trying to *
* create such long files are not very *
* descriptive. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following are possible places where we might run into the
file path limit problem on Windows:
(1) cell level config repository
(2) node level config repository
(3) workspace (WAS_HOME/wstemp/workspace_id folder)
(4) application install directory
(WAS_HOME/installedApps/appname folder by default)
This APAR, however, does not address all of these scenarios.
This is due to performance cost that would be involved to
consider all cases.
This APAR checks the path of application files created in
(1) cell level config repository and (3) workspace. The
following error message will be displayed for files that
exceeds the limit and application install will fail:
"The URI length is greater than the Windows limit of 259
characters. The file, {file name}, may need to removed
manually."
Problem conclusion
Added checkes in application deployment and workspace to
handle file creation failures due to file path exceeding
Windows limit during application deployment. The scenarios
covered here are:
-- file creation in cell level repository
-- file creation in workspace
Temporary fix Comments
APAR information |
APAR number |
PQ93022 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-08-18 |
Closed date |
2004-10-19 |
Last modified date |
2005-06-10 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|