APAR status
Closed as program error.
Error description
This is a defect is similar to
PQ93022 but happens when a node
is federated to DMgr. The Application Server stores
application related data in the directories wstemp, config ,
and installedApps. Those directory structures can get very
deep. In such a scenario multiple problems can occur during
the federation of the node to a cell. The cellname is longer
then the dummy cellname used on the node and the new filenames
get too long for Windows to handle. A similar problem happens
if the DMgr. was installed in a deeper directory then the
node. A third possible reason would be in a heterogeneous
network. We could have an application installed on a node
running UNIX and the DMgr. running on Windows or the other way
around. In both cases we might get problems when an
application is copied from one machine to the other.
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 federating a node into a *
* dmgr running on Windows, it is *
* possible the deployed application *
* files will reach this path limit. *
* Currently, there is no check performed *
* or a descriptive message. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When federating a node into a Network Deployment environment
with -includeapps option, deployed applications will be
uploaded to the master repository. If the paths of the
application files are longer than Windows path limit of 259
characters, such applications will not be uploaded
successfully, and users will not be able to administrate them
afterwards. Therefore, a check is needed to detect this
scenario. Such applications should not be uploaded and an
error message should be reported during node federaton.
Problem conclusion
Added a check in node federation utility to detect
applications whose file paths may exceed Windows path limit
when uploaded into the master repository.
The following error message will be displayed during node
federation:
The length of the file path is greater than the Windows limit
of 259 characters. Application is not uploaded.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.10 and 5.1.1.3. Please refer to the Recommended
Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&
context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ94206 |
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-09-14 |
Closed date |
2004-11-15 |
Last modified date |
2004-11-15 |
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 |
|