Check again (I think André's) hint about JkMountCopy.
Regards,
Rainer
On 02.12.2009 17:33, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vas,
On 12/2/2009 11:06 AM, groupalias v wrote:
In response to Chris' question - I have only one tomcat instance
running and it picks up the webapps in /srv/tomcat6/webapps/
and the URL www.example.com:8080/test/index.jsp works fine.
- From what you posted earlier, you have a webapp in
/srv/tomcat6/webapps/A, which should be accessed via a URL such as:
http://www.example.com:8080/A/index.jsp
If you have a webapp deployed into /srv/tomcat6/webapps/test, you didn't
mention it (and it's important information). If you have no webapp
deployed into /srv/tomcat6/webapps/test, then it will use the default
webapp which will be in /srv/tomcat6/webapps/ROOT unless otherwise
configured. If you have neither of these, I would fully expect to get a
400 error because http://www.example.com:8080/test does not map to any
configured webapp.
I tried with the mod_jk.c and jk_module with the same result.
I don't think mod_jk is the problem, here.
Tomcat does not produce a log message when a webapp cannot be found, and
you can see mod_jk returning a 400 from Tomcat. I believe this is a
webapp deployment problem.
What is the workers.tomcat_home directive in workers.properties used for?
Nothing. It is an old configuration option that is no longer used.
If the communication is over the 8009 port why does apache care about
one of tomcat's directories?
It doesn't.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksWlvEACgkQ9CaO5/Lv0PAKZwCfXF9s/CPm/PQaugiJrifo8sR8
zikAoK8Hm0th6+x162SE7AxajlsBXkNL
=95Ua
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
