It's not that hard (always easy when you know how!). 1 question: is port 5080 where apache is listen on? looking at your httpd.conf it seem your trying to do something complex before trying the easy standard one.
Have you tried (providing that you have the examples servlets): WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples and then point your browser to http://localhost/examples/snoop Dom -----Original Message----- From: Ken Corey [mailto:[EMAIL PROTECTED]] Sent: 07 February 2002 10:18 To: Tomcat Users List Subject: Is Apache <-warp-> Tomcat a Myth? Hi All, I'm having such a huge amount of trouble with this, I'm hoping someone can suggest something. It just doesn't make sense...it's like software engineering...I was 90% of the way there in 1 hour, but the final 10% has taken me another 12 hours, and it still doesn't work! I've got a Linux 2.2.19 box (pre glibc-2.2, so prebuilds depending on glibc-2.2 won't work). I'm running Apache 1.3.20, and Tomcat 4.0.1, jdk 1.3.0. I've compiled my own warp connector module, and set everything up as per the sun web page here: http://dcb.sun.com/practices/howtos/tomcat_apache.jsp which I thought was going to provide everything I needed. My httpd.conf file has: LoadModule webapp_module libexec/mod_webapp.so WebAppConnection warpConnection warp js1.atomic-interactive.com:8008 WebAppDeploy sample warpConnection /sample/ I went through the development process as outlined on the tomcat site, so now, I've got a lovely little project directory (hello world, of course), a web.xml that specifies the servlet. The project is called 'sample'. (NOTE: 213.165.155.8 as shown below *is* js1.atomic-interactive.com shown above. I could see no difference in my tests one way or another, as I don't have virtual hosts turned on in Apache.) So, after a deploy and a tomcat restart, my tomcat application can now be seen: http://213.165.155.8:8080/sample The index.html page is pulled up, and when the link is clicked it takes the user to the servlet served up by Tomcat. http://213.165.155.8:8080/sample/hello Now, let's try this on Apache 1.3.20: http://213.165.155.8:5080/sample Nothing is shown in Tomcat's logs, and so apache tries to offer the index.html, which of course doesn't exist as far as Apache is concerned. http://213.165.155.8:5080/sample/ tomcat 'sees' this one, judging by the logs: 2002-02-07 09:40:48 WarpEngine[js1.atomic-interactive.com]: Mapping request 2002-02-07 09:40:48 WarpHost[js1.atomic-interactive.com]: Mapping request for Host 2002-02-07 09:40:48 StandardContext[/sample]: Mapping contextPath='/sample' with requestURI='/sample/' and relativeURI='/' 2002-02-07 09:40:48 StandardContext[/sample]: Decoded relativeURI='/' 2002-02-07 09:40:48 StandardContext[/sample]: Trying exact match 2002-02-07 09:40:48 StandardContext[/sample]: Mapped to servlet 'default' with servlet path '/' and path info 'null' and update=true 2002-02-07 09:40:48 default: DefaultServlet.serveResource: Serving resource '/' headers and data However, tomcat apparently denies any knowlege, so Apache tries to load the index.html file, which still doesn't exist: http://213.165.155.8:5080/sample/index.html Strangely, though, the servlet still does exist: http://213.165.155.8:5080/sample/hello So what gives? -Ken -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
