Bug 889395
Summary: | Tomcat adds colon to the beginning of the classpath; problem with automount | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andreas Girgensohn <andreasg123> |
Component: | tomcat | Assignee: | Ivan Afonichev <ivan.afonichev> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | akurtako, ivan.afonichev, java-sig-commits, kdaniel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-12 01:06:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andreas Girgensohn
2012-12-21 03:19:23 UTC
A colleague suggested putting a CLASSPATH entry into /etc/tomcat/tomcat.conf as a workaround. That works as long as the file or directory exists. E.g., "/tmp" works but using "aa.jar" causes a FileNotFoundException. While the classpath is the most serious problem, it would make more sense to use $CATALINA_HOME instead of "/" as the current working directory for the service. That would avoid the problem with "/net", too. tomcat-7.0.34-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tomcat-7.0.34-1.fc18 Package tomcat-7.0.34-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tomcat-7.0.34-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20939/tomcat-7.0.34-1.fc18 then log in and leave karma (feedback). If you can also provide a Fedora 17 version, I'll test it and leave karma. Build of 7.0.34 for f17 http://koji.fedoraproject.org/koji/taskinfo?taskID=4817874 is blocked by not yet pushed to stable https://admin.fedoraproject.org/updates/FEDORA-2012-16497/ecj-4.2.1-1.fc17 You can test it and leave karma there. (In reply to comment #6) > Build of 7.0.34 for f17 > http://koji.fedoraproject.org/koji/taskinfo?taskID=4817874 is blocked by not > yet pushed to stable > https://admin.fedoraproject.org/updates/FEDORA-2012-16497/ecj-4.2.1-1.fc17 > > You can test it and leave karma there. It looks like the build failed, maybe because ecj-4.2.1-1.fc17 is needed. tomcat-7.0.34-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Why did this bug get closed? There isn't a version available for testing in Fedora 17. Fedora 18 will only be released next week. ecj-4.2.1-2.fc17.x86_64 is in testing. It works for me with tomcat-7.0.33-2.fc17. Please build tomcat-7.0.34-1.fc17 using the test version of ecj. tomcat-7.0.35-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/tomcat-7.0.35-1.fc17 tomcat-7.0.37-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/tomcat-7.0.37-1.fc17 tomcat-7.0.37-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tomcat-7.0.37-1.fc18 tomcat-7.0.37-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |