PQ77134: Websphere App Server 5.0.2 does not accept SymLink in Ear directory | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Problem description: After upgrading to Websphere App Svr fixpack 5.0.2, when attempting to install web applications using an unpacked EAR directory with a symlink to the real directory that contains the unpacked war file, it fails. However, if the contents of the unpacked war file are copied into the EAR directory (i.e. not using a symlink), everything works fine. This is a regression from WAS5 and WAS5.0.1Local fix test fix has been createdProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users * * installing applications that use symbolic * * links on a UNIX platform. * **************************************************************** * PROBLEM DESCRIPTION: Using symbolic links to represent * * modules in installed applications fails * * at startup. * **************************************************************** * RECOMMENDATION: * **************************************************************** A regression had been introduced with a fix for a previously reported problem with double file separators in configuration files. The fix for that problem was to canonicalize the file path before opening modules. Canonicalizing the path causes symbolic links to fail. The fix for this is not to use canonical paths in the case of symbolic links. The symptom of is this problem is a runtime exception, for example: ---- Begin backtrace for nested exception ModuleRefImpl.com.ibm.etools.archive.exception. NoModuleFileException: A file does not exist for module element having uri: xxx.war at com.ibm.etools.commonarchive.impl. ModuleRefImpl.checkType(ModuleRefImpl.java:715) at com.ibm.etools.commonarchive.impl. ModuleRefImpl.initModuleFileFromEAR(ModuleRefImpl.java:270) at com.ibm.etools.commonarchive.impl. ModuleRefImpl.getModuleFile(ModuleRefImpl.java:247)Problem conclusion The relevant common archive classes were updated to correctly handle symbolic links.Temporary fix Two interim fixes, PQ77134_5.0.1 and PQ77134_5.0.2 are now being tested.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00I
Software edition:
Reference #: PQ77134
IBM Group: Software Group
Modified date: Aug 14, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.