Hi all...
> From: Dmitri Colebatch <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], Richard Richter <[EMAIL PROTECTED]>
> Subject: Re: JkMount in httpd.conf
> Date: Thu, 28 Jun 2001 09:17:15 +1000
>
> Richard,
> sorry for the latency here... our connection is proving a right pain...
No matter of time. ;-)
> > Here (you wrote similar advice "Re: Servlet configuration" to somebody
> > else) I looked to web.xml, which contains:
> >
> > <servlet>
> > <servlet-name>Hello</servlet-name>
> > <servlet-class>Hello</servlet-class>
> > </servlet>
> >
> > <servlet>
> > <servlet-name>HelloServlet</servlet-name>
> > <servlet-class>Hello</servlet-class>
> > </servlet>
> >
> > <servlet-mapping>
> > <servlet-name>HelloServlet</servlet-name>
> > <url-pattern>/hello</url-pattern>
> > </servlet-mapping>
> >
> did I write that? shit. there should only be one <servlet> ... </servlet>
> entry per servlet _name_ (although you can deploy the same servlet class as
> different servlets and use different parameters to achieve different
> behaviour). So if you remove the first of the two <servlet> ... </servlet>
> entries it would be correct.
OH SORRY... I didn't want to say that you gave advice with TWO servlet tags - no
YOU DIDN'T... The fact that two are too much wasn't known to me - you know,
example of web.xml is the only thing I have to learn from. ;-)))
This was web.xml of one of my mate in work - I was just trying to let it run as
admin of Tomcat ;-)...
Now I can see that I have to write it from scratch or something... ;-)
> > Maybe there is some redundancy or missing... but where? Because Hello.class
> > is in webapps/intranet/WEB-INF/classes (with all classes generated from
> > jsps) and web.xml is in WEB-INF... that's right I hope. URI is still the
> > same:
> [sidenote] the JSPs get compiled in the $TOMCAT_HOME/work directory, unless
> you're compiling them yourself (which I dont think there's any reason to)
> they shouldn't be in the WEB-INF/classes directory.
>
> > host:port/intranet/servlet/hello
> ok - I'm a bit frazzled here because its been a while since I last wrote
> about this, so let me refresh my mind...
>
> I'm assuming you have tomcat available as well? Assuming you're running both
> on the same box... can you request
> http://localhost:8080/intranet/servlet/hello (straight through tomcat).
Okey, I blow up comments of Httpblabla... in server.xml and tried it - and
EVERYTHING works. So now there is a question why localhost:8080 functions and
my.virtual.host:port don't (BUT ONLY FOR SERVLETS! - jsps are good). I don't
wanna use tomcat as standalone...
BTW: /intranet/hello was right path, I don't see what are the lines with
/.../servlet/hello for (in mod_jk.conf-auto) - but this is detail. ;-)
> When I get frustrated I do a "tail -f logs/*" and see if that helps me (o:
> not sure if that'll be any help... anyway I think the approach should first
> be to check that everything is working in standalone.
So - after your last mail I woke up and I'm checking logs now... but all at all
- the only thing I see is in mod_jk.log well known two lines:
[jk_uri_worker_map.c (344)]: Into jk_uri_worker_map_t::map_uri_to_worker
[jk_uri_worker_map.c (434)]: jk_uri_worker_map_t::map_uri_to_worker, done
without a match
> cheesr
> dim
Another "so" - so where is the differences between Apache-mod_jk-Tomcat and
standalone Tomcat? I mean differences in servlet processing. On localhost:8080
everything runs perfectly and via virtual host of Apache and mod_jk... only jsp.
But - as I can see now - servlet request is redirected - jk_uri_worker_map can't
resolve it and Apache then sends obvious Not found. Hm...
Thank you for care :-)
Virgo
Richard Richter ([EMAIL PROTECTED])
Application Programmer, Business Global Systems a. s.
