Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added help with Vista related issues

...

  1. Wiki Markup
    \[#Q1 Why do I get Out of Environment Space?\]
  2. Wiki Markup
    \[#Q2 When I start up tomcat (or when it is running), I get the error java.lang.IllegalMonitorStateException: current thread not owner\]
  3. Wiki Markup
    \[#Q3 Can I turn off case sensitivity?\]
  4. Wiki Markup
    \[#Q4 Can I use NTLM authentication?\]
  5. Wiki Markup
    \[#Q5 I want to redeploy web applications, how do I prevent resources from getting locked?\]
  6. Wiki Markup
    \[#Q6 Can I use UNC paths?\]
  7. Wiki Markup
    \[#Q7 Why can't Tomcat see my mapped drive when running as a service?\]
  8. Wiki Markup
    \[#Q8 Why aren't access logs showing up in Tomcat on Vista?\]
  9. Wiki Markup
    \[#Q9 Why do I get a "HTTP/1.x 400 No Host matches server name" error when I change the "webapps" folder in Tomcat on Vista?\]
    \\

Answers

Why do I get Out of Environment Space?

...

The mapped drives are part of a user's profile and they are not used when running as a service. You should be OK with UNC paths.

Why aren't access logs showing up in Tomcat on Vista?

By default, the Tomcat Windows Service installer attempts to place Tomcat inside the "Program Files" folder. Default Vista folder permissions cause various logging functions (though mysteriously not every log function) to fail silently. It is best to change Tomcat's install folder to something like "C:\Tomcat". This issue can be hard to spot because by default the access logs are not enabled and the example webapps work just fine.

Why do I get a "HTTP/1.x 400 No Host matches server name" error when I change the "webapps" folder in Tomcat on Vista?

Wiki Markup
By default, the Tomcat Windows Service installer attempts to place Tomcat inside the "Program Files" folder.  Default Vista folder permissions conflict with the contents of the "webapps" folder, can case a blank page to come up when attempting to access the webapp.  By using a HTTP Header inspector like "\[https://addons.mozilla.org/en-US/firefox/addon/3829 Live HTTP Headers\]" you can see a slightly more descriptive error message.  It is best to change Tomcat's install folder to something like "C:\Tomcat".  This issue can be hard to spot because by default the example webapps work just fine.