Thx for the replies. I'm using 4.1.29. I haven't played anything with the structure at all. The strange thing is that when I put the test.jsp file in the examples folder in webapps I can display it and it works like a charm, but if I put it anywhere else it wont work. Putting it in ROOT does not help this at all.
So what permissions do I need to have on the file? this is my web.xml file <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";> <web-app> <display-name>Welcome to Tomcat</display-name> <description> Welcome to Tomcat </description> </web-app> I haven't changed anything in it. Adding JkMount /*.jsp aj13 to my mod_jk.conf had the wanted effect. I can now see http://localhost:8080/test.jsp . But there's still no formatation on test.jsp on port 80 :(, atleast now we know that tomcat is working properly. Guy Rouillier said before that I have to make sure that 'tomcat is set up properly by going directly to it for the JSP page, bypassing Apache', how would I check this? And how do I set it up? ./Lukas ----- Original Message ----- From: "Jeff Tulley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 26, 2004 11:25 PM Subject: Re: mod_jk problem > Lukas, > I haven't been following this thread too closely....so maybe I've > missed some of your earlier explanation... > If you are going through port 8080, there is no mod_jk or mod_jk2 > involved, and the problem is probably elsewhere - for instance maybe > your web application is not set up properly(wrong directory structure?), > or there are file permission problems on your directories or your > web.xml file. I have a coworker who had these type of file permission > problems twice in the last few weeks, and it was not immediately obvious > that this was the problem. Or maybe your web.xml is not valid. > > When you go back to using mod_jk, be aware that the command in apache > for mod_jk is more like: > > JkMount /*.jsp ajp13 > > You do not embed this in a location tag necessarily. > > But get things working through port 8080 first before tackling Apache > integration. Like you said you just want to get started with JSP > without the battle. > > > >>> [EMAIL PROTECTED] 1/26/04 2:35:24 PM >>> > Ok, now I'm really getting confused, I put the test.jsp file in > $CATALINE_HOME/webapps/test.jsp and when doing > http://localhost:8080/test.jsp in links (can't open my 8080 port > yet...) I > get a file cannot be found message, but when I look at the example > folder > they show as they should. Anyone who knows what I'm doing wrong? > > Also when adding > > <Location "/*.jsp"> > JkUriSet worker ajp13:localhost:8009 > </Location> > > to my http.conf file I got an error message that said that apache > couldn't > recongnixe JkUriSet. Is that because JkUriSet is only availabel in jk2 > or??? > > ./Lukas > > ----- Original Message ----- > From: "Guy Rouillier" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Monday, January 26, 2004 9:39 PM > Subject: RE: mod_jk problem > > > Lukas Larsson wrote: > > Thx for the reply. I folloes your second link and found this site > > (http://johnturner.com/howto/apache2-tomcat4127-jk-rh9-howto.h > > tml) on how to configure mod_jk but I still get the same > > problem. Apache says that it is working with mod_jk, but it > > does not translate *.jsp pages (see > > http://garazdawi.homeftp.net/test.jsp for an > example of what > > I mean). Can someone please tell me what I'm doing wrong. I > > would really want to get started with jsp without having to > > battle with mod_jk. > > Make sure your Tomcat is set up properly by going directly to it for > the > JSP page, bypassing Apache, e.g., > http://garazdawi.homeftp.net:8080/test.jsp (assuming you left Tomcat > on > the default HTTP port.) If that doesn't work, then the problem is in > Tomcat configuration not in mod_jk. > > Jeff Tulley ([EMAIL PROTECTED]) > (801)861-5322 > Novell, Inc., The Leading Provider of Net Business Solutions > http://www.novell.com > > --------------------------------------------------------------------- > 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]
