https://issues.apache.org/bugzilla/show_bug.cgi?id=50737
--- Comment #4 from Jon E. <j...@jonericson.com> 2011-02-11 14:51:27 EST ---
The problem occurs when Tomcat (on the iSeries / System i / AS400) is started
with a command line that has different case values than where the file system
resides.
We configured the IBM System i to start Tomcat with the following QShell
command:
qsh cmd('/Apache/apache-tomcat-6.0.32/bin/startup.sh')
Yet the real name where Tomcat resides is:
/apache/apache-tocmat-6.0.32/bin/startup.sh
Deployment fails when they are not equal, even though Tomcat is running.
In ExpandWar, when it compares the canonical paths, the
expandedFile.getCononicalPath() value is the value that was used to start
Tomcat, and the canonicalDocBasePrefix is set to the value of where the .jar
file entries reside on the file system.
/Apache/apache-tomcat-6.0.32/bin/startup.sh !=
/apache/apache-tomcat-6.0.32/bin/startup.sh
Previously we were using Tomcat 6.0.20, which did not have this validation in
class ExpandWar. On hosts that do not have case sensitive file systems, should
the path names all be resolved to lower case before this check?
WORK AROUND: On our system, we changed the command string that starts Tomcat
to be exactly the same, case-for-case, as the directory in which it resides.
When this is done, deployment works fine.
Thank you for your help.
- Jon
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
