Summary: | When using startup.bat if apache-tomcat-7.0.xx is in directory with "," (comma) or ";" (semi-colon) Tomcat fails to start | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | Rodney Beede <business2008+issues.apache.org> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED WONTFIX | ||
Severity: | minor | CC: | business2008+issues.apache.org |
Priority: | P2 | ||
Version: | 8.0.x-trunk | ||
Target Milestone: | ---- | ||
Hardware: | PC | ||
OS: | All |
Description
Rodney Beede
2013-10-02 16:36:43 UTC
Comma causes problems because Tomcat uses it as a separator in .loader properties in catalina.properties. Semi-colon causes problems because it is the separator for class path entries on Windows. Colon will probably cause a problem on non-Windows platforms as it is used as the class path separator there. I'm moving this to Tomcat 8 as I don't think there is sufficient demand from the user community for this feature in Tomcat 7 and there is a small chance that the changes necessary to support it will break something. I have fixed the comma case for 8.0.x and this will be include in 8.0.0-RC4 onwards. I'm still looking at semi-colon and colon. Having dug through the OpenJDK code there is no way Tomcat can support ; or ; in CATALINA_HOME and CATRALINA_BASE as the JRE doesn't provide any mechanism for quoting ; or : so they can't be distinguished from path separators. I'm resolving this as WONTFIX to make clear that elements of this bug can't - therefore won't - be fixed. It might be worth doing a check in catalina.bat and catalina.sh for those characters in either of CATALINA_HOME or CATALINA_BASE, and refusing to even attempt to start under those conditions. Any objections? None here. Checks added. Aw. I had a patch waiting to be committed. Mine would have worked under Cygwin, too ;) |