| Summary: | Application base [...] for host [localhost] does not exist or is not a directory | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Violeta Georgieva <milesg78> |
| Component: | snaps | Assignee: | Glyn Normington <glyn.normington> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | trivial | ||
| Priority: | P3 | CC: | eclipse, glyn.normington |
| Version: | 3.0.1.RELEASE | ||
| Target Milestone: | 3.5.1.RELEASE | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Violeta Georgieva
In tomcat-server.xml there was not Host's attibute "appBase". So Tomcat sets "webapp" as a value for this attibute, but because such directory does not exits, the error message is written to the log. Virgo does not need "appBase" attribute, because of this we can add appBase="" to the Host configuration in tomcat-server.xml (In reply to comment #1) > In tomcat-server.xml there was not Host's attibute "appBase". So Tomcat > sets "webapp" as a value for this attibute, but because such directory does not > exits, the error message is written to the log. Virgo does not need "appBase" > attribute, because of this we can add appBase="" to the Host configuration in > tomcat-server.xml Correction to my previous comment. We have appBase="webapps" in tomcat-server.xml In Virgo we do not need this attribute so we can set it like this appBase="" Change is tested, committed and pushed. Commit IDs: - org.eclipse.virgo.apps - 5764950d52e2fc556510e97c0e83bd4b8c661862 - change is in test's resources - org.eclipse.virgo.web - cf8ce5dae8e0838b43e48c3e0fc24df8b102d842 - change is in test's resources - org.eclipse.virgo.web-server - 1801e47ed31e10aef18ef7d8feeed6dac8e7b732 - change in the default tomcat-server.xml that is provided with Virgo Tomcat Server distribution Also changed in system verification tests a3dd9605b75c09967c6eb834106ac6bf8fb110d2. Another SVTs commit 4a2ef02cc06b8dff03a52656107f61fc4b3b8aa5 to make this configuration match that in use elsewhere. This also needs to be fixed in the Snaps integration tests. (In reply to comment #6) > This also needs to be fixed in the Snaps integration tests. Fixed in snaps commit f89907b9058e5ad566e923a1e157ea81167a1b5e. |