YES - it is possible :-) Inserted JkMount /servlet/* ajp13 in mod_jk.conf and now the servlet is accessible via port 80 too.
The only question left is why I get still following error messages in catalina.out when I restart TomCat?: "org.xml.sax.SAXParseException: The content of element type "web-app" must match (icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". Thanks for your help and regards Volker Volker schrieb: > I put additinally following directives in my web.xml under > /tomcat/webapps/ROOT/WEB-INF/: > > <servlet-mapping> > <servlet-name>invoker</servlet-name> > <url-pattern>/servlet/*</url-pattern> > </servlet-mapping> > > NOW http://ww.MyDomain.com:8080/servlet/HttpTunnelingServletdc request the correct > servlet (via port 8080!) > (/tomcat/webapps/ROOT/WEB-INF/classes/com/net/chat/util/tunnel3/HttpTunnelingServlet.class) > > But the same URL via port 80 still produces a 404 error although the other example > servlets of TomCat 4.1.24 work via port 80 (mod_jk ist installed). > > Is it possible that I have to add further alias directives in mod_jk.conf to make a > request via port 80 - that means > http://ww.MyDomain.com:80/servlet/HttpTunnelingServletdc - successful too? > > Best regards and thanks > > Volker > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
