Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification.
The "FAQ/Windows" page has been changed by dB.. http://wiki.apache.org/tomcat/FAQ/Windows?action=diff&rev1=8&rev2=9 -------------------------------------------------- <<Anchor(Q4)>>'''Can I use NTLM authentication?''' - With help from the Samba folks, [[http://jcifs.samba.org/src/docs/ntlmhttpauth.html|it is possible]]. + Yes. + + * [[http://waffle.codeplex.com/|Waffle/JNA]] + * [[http://tomcatspnego.codeplex.com/|Tomcat SPNEGO]] + * [[http://spnego.sourceforge.net/|SPNEGO SF]] + * [[http://www.ioplex.com/jespa.html|Jespa]] (commercial) + * [[http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html|Tomcat IIS Connector]] + * [[http://jcifs.samba.org/src/docs/ntlmhttpauth.html|Samba JCIFs]] (obsolete, no NTLMv2) <<Anchor(Q5)>>'''I want to redeploy web applications, how do I prevent resources from getting locked?''' @@ -38, +45 @@ Since Tomcat 5.0, a mechanism exists to prevent locking when accessing resources using the getResource method of the URLClassLoader. Many applications, such as Xerces, do not set the use of caching to false before opening the URL connection to a JAR file, and that causes locking. In Tomcat 5.5, this mechanism is disabled by default (as it has a non negligible influence on startup times, and is often useless), and can be enabled using the `antiJARLocking` attribute of the [[http://tomcat.apache.org/tomcat-6.0-doc/config/context.html|Context]] element. If getResource call occurs, resources inside the JARs will be extracted to the work directory of the web application. There is an alternative to this since Tomcat 6.0.24: you can configure a [[http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/core/JreMemoryLeakPreventionListener.html|JreMemoryLeakPreventionListener]] in your `server.xml` and it will set the URL connection caching to be off by default. - There is another lock prevention mechanism in Tomcat 5.5 (`antiResourceLocking` attribute), which will cause the web application files to be copied to the temp folder and run from this location. This has a larger impact on web application startup times, but obviously prevents locking on all resources of the web application. This also allows more flexible management operations as none of the web application resources will be locked, even while the web application is running (as a special note, when making changes to JSPs without reloading the application, the changes have to be duplicated to the path where the web application resources have been copied in the temp folder). + There is another lock prevention mechanism in Tomcat 5.5 (`antiResourceLocking` attribute), which will cause the web application files to be copied to the temp folder and run from this location. This has a larger impact on web application startup times, but obviously prevents locking on all resources of the web application. This also allows more flexible management operations as none of the web application resources will be locked, even while the web application is running (as a special note, when making changes to JSPs without reloading the application, the changes have to be duplicated to the path where the web application resources have been copied in the temp folder). <<Anchor(Q6)>>'''Can I use UNC paths?''' @@ -50, +57 @@ <<Anchor(Q8)>>'''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. + 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. <<Anchor(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?''' - 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. + 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. <<Anchor(Q10)>>'''How do I add or customize a Windows Service for Tomcat?''' - Tomcat uses the Apache Commons Daemon. You can read its documentation at http://commons.apache.org/daemon/procrun.html As a short example, you can create a new Windows Service with the full version number in its name like this: + Tomcat uses the Apache Commons Daemon. You can read its documentation at http://commons.apache.org/daemon/procrun.html As a short example, you can create a new Windows Service with the full version number in its name like this: {{{bin\tomcat6.exe //IS//tomcat6026 --DisplayName "Apache Tomcat 6.0.26"}}} See also the `service.bat` file that comes in the `*-windows-<arch>.zip` distributives of Tomcat. ---- - [[CategoryFAQ|CategoryFAQ]] + [[CategoryFAQ]] + --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
