Discussion:
Tomcat and apache and jk_mod HowTo
Tim Potter
2008-10-10 15:54:34 UTC
Permalink
Hello all,

Be kind, this is my first mailing to the usergroup.

I am implementing a webserver for a group use, where most of the group will
be creating web pages with php and jsp connections.

This server is running Ubuntu Gutsy (7.10) and may be updated to Hardy
shortly. In the mean time, currently I'm running apache/2.2.4 with the
mod_user module enabled, and people in the group using public_html
directories to serve their web pages.

I have come to expect that not many in the group will be utilizing jsp as
the scripting language of choice, but would like it to be available, thus I
am trying to implement tomcat and a connector with jk_mod to apache.

I have successfully setup Tomcat (version 6.0.18) with Java 1.6.0_03
(Java(TM) SE Runtime Environment (build 1.6.0_03-b05)), and I have
downloaded the mod_jk-1.2.23-apache-2.2.x-linux-i686.so module and symlinked
/usr/lib/apache2/modules/mod_jk.so to that file.

BTW: I have also setup the user webapp access successfully and can connect
to http://localhost:8090/~username/webapp.jsp

I planned to use this HowTo to get mod_jk configured in Tomcat and Apache,
but am seeing different references and believe this article might be a few
versions behind:
http://tomcat.apache.org/connectors-doc/generic_howto/quick.html

This section:

Here is the minimum which should be set in httpd.conf directly or included
from another file:

# Load mod_jk module
# Update this path to match your modules location
LoadModule jk_module libexec/mod_jk.so
# Declare the module for <IfModule directive> (remove this line on Apache
2.x)
AddModule mod_jk.c
# Where to find workers.properties
# Update this path to match your conf directory location (put
workers.properties next to httpd.con$
JkWorkersFile /etc/httpd/conf/workers.properties
# Where to put jk shared memory
# Update this path to match your local state directory or logs directory
JkShmFile /var/log/httpd/mod_jk.shm
# Where to put jk logs
# Update this path to match your logs directory location (put mod_jk.log
next to access_log)
JkLogFile /var/log/httpd/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# Select the timestamp log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
# Send everything for context /examples to worker named worker1 (ajp13)
JkMount /examples/* worker1


I believe there should be some changes to these instructions, and I would
ask that someone with more knowledge than me give me validation and any
pointers to ensuring that this works as planned.

I am creating a file called /etc/apache2/conf.d/mod_jk.conf that contains
the above information with the alterations as follows:
change libexec/mod_jk.so to /usr/lib/apache2/mod_jk.so
comment out the AddModule mod_jk.c line
repace all instances of httpd with apache2
and point the JkWorkersFile to /etc/apache2/conf.d/workers.properties

Does this make sense?

Also, I've interpreted from
http://tomcat.apache.org/connectors-doc/generic_howto/workers.html
that the workers.properties file should be in $CATALINA_HOME/conf/ is
this not correct?

Is there anything else that needs to be done, other than restarting apache2
and tomcat?

I attempted these changes and stopped tomcat and apache, then started apache
and got the following error:

***@serverbox:~$ sudo /etc/init.d/apache2 start
* Starting web server apache2
Syntax
error on line 2 of /etc/apache2/conf.d/workers.properties:
Invalid command 'worker.list=worker1', perhaps misspelled or defined by a
module not included in the server configuration
[fail]
I've looked at the log and no jk log is being created, and the error log
doesn't have anything after stopping the apache daemon. Any help would be
greatly appreciated.

Thanks!
Rainer Jung
2008-10-10 16:28:38 UTC
Permalink
Post by Tim Potter
Be kind, this is my first mailing to the usergroup.
I'll do my best.
Post by Tim Potter
This server is running Ubuntu Gutsy (7.10) and may be updated to Hardy
shortly. In the mean time, currently I'm running apache/2.2.4 with the
mod_user module enabled, and people in the group using public_html
directories to serve their web pages.
I have come to expect that not many in the group will be utilizing jsp as
the scripting language of choice, but would like it to be available, thus I
am trying to implement tomcat and a connector with jk_mod to apache.
I have successfully setup Tomcat (version 6.0.18) with Java 1.6.0_03
(Java(TM) SE Runtime Environment (build 1.6.0_03-b05)), and I have
downloaded the mod_jk-1.2.23-apache-2.2.x-linux-i686.so module and symlinked
/usr/lib/apache2/modules/mod_jk.so to that file.
Not relevant concerning your observations, but when you start something
new, you shouldn't use old version without good reasons. Apache httpd is
at 2.2.9 (soon 2.2.10) and mod_jk is at 1.2.26. Java 6 is at 1.6.0_07.
Post by Tim Potter
BTW: I have also setup the user webapp access successfully and can connect
to http://localhost:8090/~username/webapp.jsp
Fine.
Post by Tim Potter
I planned to use this HowTo to get mod_jk configured in Tomcat and Apache,
but am seeing different references and believe this article might be a few
http://tomcat.apache.org/connectors-doc/generic_howto/quick.html
Here is the minimum which should be set in httpd.conf directly or included
# Load mod_jk module
# Update this path to match your modules location
LoadModule jk_module libexec/mod_jk.so
The default directory is libexec for httpd 1.3.x and modules for httpd
2.x. You can put any path here as long as the file is there. You can
even point directly to the versioned file you downloaded without using
any symlink.
Post by Tim Potter
# Declare the module for <IfModule directive> (remove this line on Apache
2.x)
AddModule mod_jk.c
Delete this for httpd 2.x.
Post by Tim Potter
# Where to find workers.properties
# Update this path to match your conf directory location (put
workers.properties next to httpd.con$
JkWorkersFile /etc/httpd/conf/workers.properties
You can put the workers.properties file anywhere you like, as long as
you put the chosen path here. You can even change it's name.

Beware: Depending on your Linux distribution, there might be magic
directories which should only contain httpd configuration files, because
the httpd configuration of your distribution might try to read in all
files in such a magic directory via Include when parsing the httpd
configuration. The error cited by you below indicates, that this is the
case here. Your httpd configuration contains an include for
/etc/httpd/conf/*, so it tries to read all files including
workers.properties although workers.properties is *not* a general httpd
configuration file, but instead a special mod_jk file. So put it
elsewhere and change the path given to JkWorkersFile accordingly.
Post by Tim Potter
# Where to put jk shared memory
# Update this path to match your local state directory or logs directory
JkShmFile /var/log/httpd/mod_jk.shm
# Where to put jk logs
# Update this path to match your logs directory location (put mod_jk.log
next to access_log)
JkLogFile /var/log/httpd/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# Select the timestamp log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
Delete the JkLogStampFormat. The default should be fine.
Post by Tim Potter
# Send everything for context /examples to worker named worker1 (ajp13)
JkMount /examples/* worker1
If you want to forward requests for the URI /examples/*, then this is
OK, else you need to put the URI here, that you are actually going to
use, e.g. JkMount /*.jsp worker1.

worker1 here is a name you can choose, but you need to define the
properties of this worker in thhe JkWorkersFile (workers.properties),
like IP, Port etc.
Post by Tim Potter
I am creating a file called /etc/apache2/conf.d/mod_jk.conf that contains
change libexec/mod_jk.so to /usr/lib/apache2/mod_jk.so
comment out the AddModule mod_jk.c line
repace all instances of httpd with apache2
and point the JkWorkersFile to /etc/apache2/conf.d/workers.properties
Does this make sense?
Yes, see above.
Post by Tim Potter
Also, I've interpreted from
http://tomcat.apache.org/connectors-doc/generic_howto/workers.html
that the workers.properties file should be in $CATALINA_HOME/conf/ is
this not correct?
You can place it in an arbitrary directory, as long as you put the path
to the file as the value to JkWorkersFile.
Post by Tim Potter
Is there anything else that needs to be done, other than restarting apache2
and tomcat?
Yes, producing a correct workers.properties file.
Post by Tim Potter
I attempted these changes and stopped tomcat and apache, then started apache
* Starting web server apache2
Syntax
Invalid command 'worker.list=worker1', perhaps misspelled or defined by a
module not included in the server configuration
[fail]
See above, this is because there is some include for any file in
/etc/apache2/conf in some of your httpd configuration files.
workers.properties is not understandable by httpd itself, only by
mod_jk, which will load it separately.

Regards,

Rainer

---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org
Tim Potter
2008-10-10 17:02:52 UTC
Permalink
Post by Rainer Jung
Post by Tim Potter
I attempted these changes and stopped tomcat and apache, then started
apache
Post by Rainer Jung
Post by Tim Potter
* Starting web server apache2
Syntax
Post by Rainer Jung
Post by Tim Potter
Invalid command 'worker.list=worker1', perhaps misspelled or defined by
a
Post by Rainer Jung
Post by Tim Potter
module not included in the server configuration
[fail]
See above, this is because there is some include for any file in
/etc/apache2/conf in some of your httpd configuration files.
workers.properties is not understandable by httpd itself, only by
mod_jk, which will load it separately.
Regards,
Rainer
Rainer,

Thanks for your prompt reply.

I was able to resolve the apache error by moving the workers.properties file
to /etc/apache2/
and changing the relevant reference in /etc/apache2/conf.d/jk_mod

I also added <Listener className="org.apache.jk.config.ApacheConfig"
modJk="/usr/lib/apache2/mod_jk.so"
workersConfig="/etc/apache2/workers.properties" /> between </Host> and
</Engine> in the conf/server.xml file

Now Apache starts successfully. I also modified jk_mod section: JkMount
/*.jsp worker1 as you suggested.

With this apache runs, and tomcat runs (as it should), however, .jsp files
are not being parsed.

Should I change the <Connector port="8090" protocol="HTTP/1.1"
to 80

Any suggestions for troube shooting this?

Aslo, can you CC me on these emails, as I am only subscribed to the digest
and don't get your message without awaiting that or checking the archives.

Thanks so much!
Rainer Jung
2008-10-10 17:16:56 UTC
Permalink
Post by Tim Potter
I also added <Listener className="org.apache.jk.config.ApacheConfig"
modJk="/usr/lib/apache2/mod_jk.so"
workersConfig="/etc/apache2/workers.properties" /> between </Host> and
</Engine> in the conf/server.xml file
The listeners are only needed if you want Tomcat to generate a mod_jk
configuration for you. The files which are auto-generated by the
listener are not very good though. I would suggest to write a simple
workers.properties yourself.

worker.list=worker1
worker.worker1.host=XXX
worker.worker1.port=YYY

XXX should by the address of the system, on which your Tomcat runs. If
it is the same as your Apache system, "localhost" should do it. You can
use names or IP address, but the name has to be resolvable during
startup of httpd.

YYY is the port number of your Tomcat AJP port. It is not the same as
the HTTP port of Tomcat (8090). You will find the port number in your
server.xml. There should be a Connector element there for the AJP
protocol. By default it is 8009.
Post by Tim Potter
Now Apache starts successfully. I also modified jk_mod section: JkMount
/*.jsp worker1 as you suggested.
If everything works, you should have a look the the "reference" docs
pages for tomcat-connectors, especially those concerning Apache and Workers.

Regards,

Rainer

---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org
Tim Potter
2008-10-10 18:20:32 UTC
Permalink
Post by Tim Potter
I also added <Listener className="org.apache.jk.config.ApacheConfig"
Post by Tim Potter
modJk="/usr/lib/apache2/mod_jk.so"
workersConfig="/etc/apache2/workers.properties" /> between </Host> and
</Engine> in the conf/server.xml file
The listeners are only needed if you want Tomcat to generate a mod_jk
configuration for you. The files which are auto-generated by the listener
are not very good though. I would suggest to write a simple
workers.properties yourself.
worker.list=worker1
worker.worker1.host=XXX
worker.worker1.port=YYY
XXX should by the address of the system, on which your Tomcat runs. If it
is the same as your Apache system, "localhost" should do it. You can use
names or IP address, but the name has to be resolvable during startup of
httpd.
YYY is the port number of your Tomcat AJP port. It is not the same as the
HTTP port of Tomcat (8090). You will find the port number in your
server.xml. There should be a Connector element there for the AJP protocol.
By default it is 8009.
Now Apache starts successfully. I also modified jk_mod section: JkMount
Post by Tim Potter
/*.jsp worker1 as you suggested.
If everything works, you should have a look the the "reference" docs pages
for tomcat-connectors, especially those concerning Apache and Workers.
Regards,
Rainer
It seems that every thing is running, however I get the Tomcat 404 error (in
the Tomcat style, not apache style) on a test page that I have put in
/var/www

***@serverbox:~$ ls -al /var/www | grep test
-rw-r--r-- 1 root root 235 2008-10-10 12:04 test.jsp

output of apache2/error.log
[Fri Oct 10 12:59:32 2008] [notice] Apache/2.2.4 (Ubuntu)
PHP/5.2.3-1ubuntu6.4 mod_jk/1.2.23 configured -- resuming normal operations
output of access.log
xxx.xxx.xxx.xxx- - [10/Oct/2008:13:00:26 -0500] "GET /test.jsp HTTP/1.1" 404
979 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; .NET CLR 2.0.50727; InfoPath.1)"
output of mod_jk.log
[Fri Oct 10 12:59:32 2008] [19584:34480] [info] init_jk::mod_jk.c (2743):
mod_jk/1.2.23 initialized
[Fri Oct 10 12:59:32 2008] [19585:34480] [info] init_jk::mod_jk.c (2743):
mod_jk/1.2.23 initialized
output of catalina.out
Oct 10, 2008 12:59:53 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386/client:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 645 ms
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Oct 10, 2008 12:59:54 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/37 config=null
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 924 ms

So It seems that the call to test.jsp is being redirected somewhere? Am I
missing something?

Thanks again!
Tim Potter
2008-10-10 18:29:41 UTC
Permalink
Post by Tim Potter
Post by Tim Potter
I also added <Listener className="org.apache.jk.config.ApacheConfig"
Post by Tim Potter
modJk="/usr/lib/apache2/mod_jk.so"
workersConfig="/etc/apache2/workers.properties" /> between </Host> and
</Engine> in the conf/server.xml file
The listeners are only needed if you want Tomcat to generate a mod_jk
configuration for you. The files which are auto-generated by the listener
are not very good though. I would suggest to write a simple
workers.properties yourself.
worker.list=worker1
worker.worker1.host=XXX
worker.worker1.port=YYY
XXX should by the address of the system, on which your Tomcat runs. If it
is the same as your Apache system, "localhost" should do it. You can use
names or IP address, but the name has to be resolvable during startup of
httpd.
YYY is the port number of your Tomcat AJP port. It is not the same as the
HTTP port of Tomcat (8090). You will find the port number in your
server.xml. There should be a Connector element there for the AJP protocol.
By default it is 8009.
Now Apache starts successfully. I also modified jk_mod section: JkMount
Post by Tim Potter
/*.jsp worker1 as you suggested.
If everything works, you should have a look the the "reference" docs pages
for tomcat-connectors, especially those concerning Apache and Workers.
Regards,
Rainer
It seems that every thing is running, however I get the Tomcat 404
error (in the Tomcat style, not apache style) on a test page that I have put
in /var/www
-rw-r--r-- 1 root root 235 2008-10-10 12:04 test.jsp
output of apache2/error.log
[Fri Oct 10 12:59:32 2008] [notice] Apache/2.2.4 (Ubuntu)
PHP/5.2.3-1ubuntu6.4 mod_jk/1.2.23 configured -- resuming normal operations
output of access.log
xxx.xxx.xxx.xxx- - [10/Oct/2008:13:00:26 -0500] "GET /test.jsp HTTP/1.1"
404 979 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET
CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)"
output of mod_jk.log
mod_jk/1.2.23 initialized
mod_jk/1.2.23 initialized
output of catalina.out
Oct 10, 2008 12:59:53 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386/client:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 645 ms
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Oct 10, 2008 12:59:54 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/37 config=null
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 924 ms
So It seems that the call to test.jsp is being redirected somewhere? Am I
missing something?
Thanks again!
I was definately on to something as I went to http://mysite/index.jsp and
got to the webapp/ROOT/index.jsp status page!! but the images are not
loading
error.log:
[Fri Oct 10 13:25:49 2008] [error] [client xxxxxxx] File does not exist:
/var/www/tomcat-power.gif, referer: http://mysite/index.jsp
I honestly do not care too much about that, I can try to fix that later.

Snow my question is how do I make the calls transparent, in that when I go
to http://mysite/~username/index.jsp it GET's from
/home/~username/public_html/index.jsp and parses the script instead of just
displays the html?
Martin Gainty
2008-10-10 19:19:35 UTC
Permalink
the way you have it configured.. test.jsp would only render if implemented in the 'ROOT' webapp of TC

I would suggest implementing a test webapp where the exact physical location of test.jsp would be
$CATALINA_HOME/webapps/test/test.jsp

Regards/
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.
Date: Fri, 10 Oct 2008 13:20:32 -0500
Subject: Re: Tomcat and apache and jk_mod HowTo
Post by Tim Potter
I also added <Listener className="org.apache.jk.config.ApacheConfig"
Post by Tim Potter
modJk="/usr/lib/apache2/mod_jk.so"
workersConfig="/etc/apache2/workers.properties" /> between </Host> and
</Engine> in the conf/server.xml file
The listeners are only needed if you want Tomcat to generate a mod_jk
configuration for you. The files which are auto-generated by the listener
are not very good though. I would suggest to write a simple
workers.properties yourself.
worker.list=worker1
worker.worker1.host=XXX
worker.worker1.port=YYY
XXX should by the address of the system, on which your Tomcat runs. If it
is the same as your Apache system, "localhost" should do it. You can use
names or IP address, but the name has to be resolvable during startup of
httpd.
YYY is the port number of your Tomcat AJP port. It is not the same as the
HTTP port of Tomcat (8090). You will find the port number in your
server.xml. There should be a Connector element there for the AJP protocol.
By default it is 8009.
Now Apache starts successfully. I also modified jk_mod section: JkMount
Post by Tim Potter
/*.jsp worker1 as you suggested.
If everything works, you should have a look the the "reference" docs pages
for tomcat-connectors, especially those concerning Apache and Workers.
Regards,
Rainer
It seems that every thing is running, however I get the Tomcat 404 error (in
the Tomcat style, not apache style) on a test page that I have put in
/var/www
-rw-r--r-- 1 root root 235 2008-10-10 12:04 test.jsp
output of apache2/error.log
[Fri Oct 10 12:59:32 2008] [notice] Apache/2.2.4 (Ubuntu)
PHP/5.2.3-1ubuntu6.4 mod_jk/1.2.23 configured -- resuming normal operations
output of access.log
xxx.xxx.xxx.xxx- - [10/Oct/2008:13:00:26 -0500] "GET /test.jsp HTTP/1.1" 404
979 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; .NET CLR 2.0.50727; InfoPath.1)"
output of mod_jk.log
mod_jk/1.2.23 initialized
mod_jk/1.2.23 initialized
output of catalina.out
Oct 10, 2008 12:59:53 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386/client:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.03/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 645 ms
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Oct 10, 2008 12:59:54 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Oct 10, 2008 12:59:54 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Oct 10, 2008 12:59:54 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Oct 10, 2008 12:59:54 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/37 config=null
Oct 10, 2008 12:59:54 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 924 ms
So It seems that the call to test.jsp is being redirected somewhere? Am I
missing something?
Thanks again!
_________________________________________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
Tim Potter
2008-10-10 21:02:11 UTC
Permalink
Post by Martin Gainty
the way you have it configured.. test.jsp would only render if implemented
=
Post by Martin Gainty
in the 'ROOT' webapp of TC
I would suggest implementing a test webapp where the exact physical
location of test.jsp would be
Post by Martin Gainty
$CATALINA_HOME/webapps/test/test.jsp
Regards/
Martin
Ok, that works fine, however that does not solve the problem I originally
had, which is getting jsp scripting support in the home directories of the
users on the same port as apache.

Essentially like php5 does with apache, being tranparent to the viewer.
André Warnier
2008-10-10 21:18:38 UTC
Permalink
Post by Martin Gainty
Post by Martin Gainty
the way you have it configured.. test.jsp would only render if implemented
=
Post by Martin Gainty
in the 'ROOT' webapp of TC
I would suggest implementing a test webapp where the exact physical
location of test.jsp would be
Post by Martin Gainty
$CATALINA_HOME/webapps/test/test.jsp
Regards/
Martin
Ok, that works fine, however that does not solve the problem I originally
had, which is getting jsp scripting support in the home directories of the
users on the same port as apache.
And your users are all nice guys, right ?
Post by Martin Gainty
Essentially like php5 does with apache, being tranparent to the viewer.
I'm not sure Tomcat is really designed for that kind of thing.
(But I'm willing to be surprised).

I can kind of imagine a forest of JkMount's on the Apache side, and a
corresponding forest of webapp dirs on the Tomcat side.
Or maybe, using a <LocationMatch ..> under Apache, with a SetHandler in
it for mod_jk woule make this easier.
And then this under Tomcat :
http://www.tuckey.org/urlrewrite/

But I'm sure someone will come up with an easier way, and probably with
a lot of "don't"s, because...


---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org

Loading...