Re: jkMount

[BuildSmart]

On Oct 29, 2007, at 10:27:21, Christopher Schultz wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

BS,

BuildSmart wrote:

jkMount /* myworker <-- your example.

It didn't work and only further proves that mod_jk lacks any real
intelligence in functionality.

You are not making any friends on this list. I need to fix your tone

increasingly stupid posts.


wasn't designed, I wouldn't start shooting my mouth off at the authors
of the code you're bastardizing.

right now before everyone lips your bozo bit and refuses to answer your Given that you are trying to hack-up a protocol to work in a way that ti

Well it sorta worked, it worked but only with localhost, none of my

didn't work.

virtual hosts worked and I lost perl and php functionality so it really

would have ".php goes to php runner, .jsp goes to Tomcat" doesn't mean
that mod_jk is broken: it means that your understanding of how to
configure it is broken.

It totally did work. You mapped everything to Tomcat, so everything went to Tomcat. Just because you wanted Apache to make the same decision you

obviously not only my understanding is broken but the advise from well intentioned helpers who direct me to make configuration by only providing partial information expecting that I know what I'm doing where tomcat is concerned.

You obviously have not read the documentation clearly, or you wouldn't
be asking these questions.

clearly I have read the documentation but it does not provide a working configuration or even an example I can copy/paste that that does anything remotely close to what I'm being told to configure.

As for only working on localhost, you need to check the rest of your
Apache httpd and Tomcat configurations: you probably don't have the

"both".

right virtual host config on either httpd or Tomcat or both. My guess is

I only have one webapp in Tomcat as localhost and it's on port 8080 (with connector on 8009) what more do I need?? Don't tell me now that I have to add an entry in Tomcat for every virtualhost that wishes to access the webapp, that makes no logical sense to have multiple tomcat virtualhosts pointing to the same webapp/docroot.

No idea, why you claim that.

Because it's true and I have seen no proof of the contrary, what I do

must be incomplete because none of the offered suggestions work.

get are well intentioned individuals offering advice however the advice

Dude, everyone uses "JkMount /*.jsp workerX". It can't be just you. Or
can it? You've been monkeying around in the mod_jk code to create this
zombie mod_just_jsp thing and now you want to complain that it doesn't
work? Get bent. You probably broke it yourself.

I'm using the mod_jk module and not a bastardized version so if it's not working per your configuration directives then it's the guys who coded mod_jk who are fault and you should bitch to them about it.

Concerning vhosts, I didn't understand, what you try to achieve.

can discuss further requirements.

Please try the above JkMount first. As soon as that works for you, we

I did, it doesn't work and it kills python and php functionality.

No, you said that "JkMount /* workerX" kills Python and Php. Rainer is
asking you to use "JkMount /*.jsp workerX".

workerX is not defined anywhere but I'll give it a try to satisfy you.



guess that doesn't work either, any more suggestion???

[Mon Oct 29 17:03:35 2007] [29592:2684415368] [debug] map_uri_to_worker::jk_uri_worker_map.c (597): Attempting to map URI '/ index.jsp' from 2 maps [Mon Oct 29 17:03:35 2007] [29592:2684415368] [debug] map_uri_to_worker::jk_uri_worker_map.c (609): Attempting to map context URI '/servlet/*=workerX' source 'JkMount' [Mon Oct 29 17:03:35 2007] [29592:2684415368] [debug] map_uri_to_worker::jk_uri_worker_map.c (609): Attempting to map context URI '/*.jsp=workerX' source 'JkMount' [Mon Oct 29 17:03:35 2007] [29592:2684415368] [debug] map_uri_to_worker::jk_uri_worker_map.c (624): Found a wildchar match '/*.jsp=workerX' [Mon Oct 29 17:03:35 2007] [29592:2684415368] [debug] wc_get_worker_for_name::jk_worker.c (115): did not find a worker workerX [Mon Oct 29 17:03:35 2007] [29592:2684415368] [error] jk_handler::mod_jk.c (2194): Could not init service for worker=workerX

Note: Jkmount by default doesn't get inhertited between vhosts,

into the vhost (or use JkMountCopy). See the docs.

because usually mounts are vhost specific. You need to put the JkMount

Putting anything into a specific vhost is a moronic concept if the
webapp is to be shared by all virtualhosts.

frustration should not result in such poor manners.

You seriously need to check yourself. While the above may be true, your

yes, you are correct, it should not, however, if it had only been a day or two of fiddling with it it wouldn't have been so bad but more than a week with incomplete directions hasn't help the frustration level, something is definitely broken if it wont work as people tell me to configure it and as you stated that is how everyone configures it and it works for them so either I'm not getting all of the information or it doesn't work. I decided to go try it on 3 other systems in the event that maybe this one is broken and it yields the same results so now that I have confirmed that it's not an isolated incident we can move forward.

I have several hundred virtual hosts and to have to configure each

one independently to access the webapp should not even be contemplated.

the ass. Php and Python are not application servers. Tomcat is an
application server and JSPs are designed to run in them. AJP is a
protocol that was designed to support this architecture. mod_jk is an


Don't complain when mod_jk and AJP don't work on your Frankenstein
architecture.

I think you're trying to do something that is just complex and a pain in implementation of that protocol also designed to support that architecture.

I'll be happy to see it work and it has nothing to do with Frankenstein architecture.

The advantages of serving the pages from the apache virtualhost
DOCUMENT_ROOT's rather than from Tomcat's webapp docroot should have
been a consideration and you can see why the concept has merrit

past their own work.

but unfortunately it seems that they have limited vision and can't see

Go talk to Sun.

I'm left with no choice but to conclude that mod_jk was someone's failed

attempt to achieve some kind of useful functionality that could be
applied in a production virtualhost environment.

Is there any other connector/module combination that has a different
result than mod_jk?

Go use mod_jk2. It may be more your style. It's got a higher version
number, so it must be better, right?

only better if you claim it is.

- -chris

-- Dale

PGP.sig
Description: This is a digitally signed message part