2010/1/19 Michael Hahn <mh...@xtivia.com>: >>isapi_redirect.dll (failing): >>(..) >> log_file=C:\tomcat\isapi_redirect.log
The above is different in the working file, log_file=C:\tomcat\logs\isapi_redirect.log > 2010-01-18 23:16:33 W3SVC1804915670 10.10.10.227 GET /servlets-examples/servlet/HelloWorldExample - 80 - 10.10.10.181 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+InfoPath.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 The above looks to me like a zero-length success (code 200) response. Why are you saying about 404? Is servlets-examples webapp deployed on the failing server? Is it running? Try accessing Tomcat directly through the HTTP connector to test that. Try looking at Tomcat Manager webapp (the URL is /manager/html and username with a role "manager" to access it is usually added to conf/tomcat-users.xml). Is the request reaching Tomcat? -- you can configure an AccessLogValve in Tomcat, see http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html The default server.xml file has an example of a configured AccessLogValve. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
