On 26.04.2010 13:56, Philip Hunt (Straker Software) wrote:
Hi,
I have the following config, to pass requests through Apache to Tomcat using
AJP:
RewriteEngine on
RewriteRule ^/abc - [L,PT]
RewriteRule (.*) /abc$1 [L,PT]
JkMount /abc/* node1
This works, to the point that requests to http
Hi,
I have the following config, to pass requests through Apache to Tomcat using
AJP:
RewriteEngine on
RewriteRule ^/abc - [L,PT]
RewriteRule (.*) /abc$1 [L,PT]
JkMount /abc/* node1
This works, to the point that requests to http://sitename/ are rewritten to
http://sitename/abc
On 15.10.2009 17:39, Christopher Schultz wrote:
Neil,
On 10/14/2009 10:43 PM, Neil Aggarwal wrote:
I then added this to my httpd.conf file in the global directives:
# Mount the jk status application
Location /jkstatus
JkMount jkstatus
Order allow,deny
Allow from all
/Location
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil,
On 10/14/2009 10:43 PM, Neil Aggarwal wrote:
I then added this to my httpd.conf file in the global directives:
# Mount the jk status application
Location /jkstatus
JkMount jkstatus
Order allow,deny
Allow from all
/Location
Try
replacing the above with:
JkMount /jkstatus jkstatus
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
worker.tomcat.socket_keepalive=True
worker.tomcat.socket_timeout=60
worker.jkstatus.type=status
worker.jkstatus.read_only=True
I then added this to my httpd.conf file in the global directives:
# Mount the jk status application
Location /jkstatus
JkMount jkstatus
Order allow,deny
Allow from all
/Location
When I go
syntax under Apache, which
is an alternative to the JkMount/JkUnmount directives :
Location /anyurl
SetHandler jakarta-servlet
SetEnvIf (some condition) no-jk
...
/Location
Full description here :
http://tomcat.apache.org/connectors-doc/reference/apache.html
(at the very bottom of the page
/crate HTTP request arrives. I keep
getting a 404 error instead.
This is the mod_rewrite directive:
RewriteRule /crate
/donors/redeem_gift_certificate.html?partner=CRATEANDBARRELutm_campaign
=CBGC [NC,PT]
I also have this mod_jk directive, which would act on either version of
the URL:
JkMount
David Crane wrote:
...
I also have this mod_jk directive, which would act on either version of
the URL:
JkMount /* worker1
Considering the above directive, then why do you have, at all :
- an Apache httpd in front of your Tomcat ? Since you are attempting to
pass everything to Tomcat
David Crane wrote:
...
I also have this mod_jk directive, which would act on either version of
the URL:
JkMount /* worker1
André Warnier wrote:
Considering the above directive, then why do you have, at all :
- an Apache httpd in front of your Tomcat ? Since you are attempting
2009/4/11 Rainer Jung rainer.j...@kippdata.de:
On 10.04.2009 23:24, J Channel wrote:
2009/4/11 Rainer Jung rainer.j...@kippdata.de
On 10.04.2009 21:41, J Channel wrote:
Hi!Apache 2.2.11, mod_jk 1.2.28
httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkOptions +ForwardURICompat
JkMount
I found that its work ok with httpd.conf like this:
...
JkMount /app/* balancer
JkUnMount /app/ntd/* balancer
...
But this is not very well cause i need to add many exception pathes
like this to httpd.conf :(
I just need to have mod_rewrite directives with more priority than JkMount.
Just like
to the DocumentRoot, you have access
to the server (or virtual server) *.conf, yes ?)
Second, I personally find another syntax clearer than JkMount, specially
when you need to combine it with other rules in Apache.
The main reason is that indeed, it is not always very clear which kind
of priority
in your main Apache configuration files.
(I suppose that if you have access to the DocumentRoot, you have access
to the server (or virtual server) *.conf, yes ?)
Second, I personally find another syntax clearer than JkMount, specially
when you need to combine it with other rules in Apache
Hi, Rainer!
Thx for you answer, its look like good solution, but anyway ignoring
line BEFORE JkMount - a bit stupid behavior.
RewriteRule ^myapp/some(.*) script.shtml%{QUERY_STRING} [L]
# Line above will be ignored
JkMount /myapp/* balancer
May be this is just a bug
RewriteRule ^myapp/some(.*) script.shtml%{QUERY_STRING} [L]
# Line above will be ignored
JkMount /myapp/* balancer
May be this is just a bug?
So, i found that its work only if condition begins with /
RewriteRule ^/myapp/some?(.*) /script.shtml?%{QUERY_STRING} [L,PT]
Other conditions
Hi!Apache 2.2.11, mod_jk 1.2.28
httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkOptions +ForwardURICompat
JkMount /app/* balancer
LoadModule rewrite_module modules/mod_rewrite.so
DocumentRoot /var/www/public_html
.htaccess in docroot:
RewriteEngine On
RewriteCond %{QUERY_STRING} !dyn\=1
On 10.04.2009 21:41, J Channel wrote:
Hi!Apache 2.2.11, mod_jk 1.2.28
httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkOptions +ForwardURICompat
JkMount /app/* balancer
LoadModule rewrite_module modules/mod_rewrite.so
DocumentRoot /var/www/public_html
.htaccess in docroot
2009/4/11 Rainer Jung rainer.j...@kippdata.de
On 10.04.2009 21:41, J Channel wrote:
Hi!Apache 2.2.11, mod_jk 1.2.28
httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkOptions +ForwardURICompat
JkMount /app/* balancer
LoadModule rewrite_module modules/mod_rewrite.so
On 10.04.2009 23:24, J Channel wrote:
2009/4/11 Rainer Jung rainer.j...@kippdata.de
On 10.04.2009 21:41, J Channel wrote:
Hi!Apache 2.2.11, mod_jk 1.2.28
httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkOptions +ForwardURICompat
JkMount /app/* balancer
LoadModule rewrite_module
* from Apache, for example,
when I access: http://apache/abc/; and http://apache/123/abc/;. The
first JkMount is trivial:
JkMount /abc ajp13_worker
JkMount /abc/* ajp13_worker
And is working as expected, but for the second... I don't have the
slightest clue on how to do it... I
the /abc/ directory; and I want to be able
to access it from *two different locations* from Apache, for example,
when I access: http://apache/abc/; and http://apache/123/abc/;. The
first JkMount is trivial:
JkMount /abc ajp13_worker
JkMount /abc/* ajp13_worker
://apache/abc/; and http://apache/123/abc/;. The
first JkMount is trivial:
JkMount /abc ajp13_worker
JkMount /abc/* ajp13_worker
And is working as expected, but for the second... I don't have the
slightest clue on how to do it... I tried mod_rewrite, but it seems
that it isn't
Hi, what to do when I want generally mount a context and it's subdirectories
with mod_jk to one worker/router, but a special subdirectory of it to a
different worker/router?
Does this work in mod_jk.conf?
JkMount /app/web/indexer worker42
JkMount /app/web/indexer/* worker42
JkMount /app
in mod_jk.conf?
|
| JkMount /app/web/indexer worker42
| JkMount /app/web/indexer/* worker42
|
| JkMount /app routerInt4
| JkMount /app/* routerInt4
This is pure speculation, but I would put your generic stuff first and
then add more-specific rules afterward.
This should be easy to test empirically
?
JkMount /app/web/indexer worker42
JkMount /app/web/indexer/* worker42
JkMount /app routerInt4
JkMount /app/* routerInt4
Do I have to write the special contextes first, so that only when they do
not match, the general mount option is used?
Thank You very mutch.
The order in mod_jk.conf
Hello,
if I want the whole apache directory tree /servlet/ and all the files and
directories within to be routed to Tomcat worker1, what of the following is
correct in mod_jk.conf?
JkMount /servlet/ worker1
JkMount /servlet worker1
JkMount /servlet/* worker1
JkMount /servlet worker1
Stephanie Wullbieter wrote:
if I want the whole apache directory tree /servlet/ and all the files and
directories within to be routed to Tomcat worker1, what of the following is
correct in mod_jk.conf?
JkMount /servlet worker1
JkMount /servlet/* worker1
(both together)
Both
You can even
I did turn out to work a little different. I did eventually change
the name of the newer applications for reasons other then described in
the problem. So the solution turned out to be a combination of a
rewriterule, proxypassreverse and a jkmount.
I did not have to change anything for the old
Hi,
It was as I expected and a virtual server was 'eating' my requests. The
JkMount was actually already set up in the global server, but by adding
the line JkMountCopy All it got forwarded to all the virtualhosts as
well. Since this is only a temporary problem for us, it will have to do
Hi Edwin,
Edwin Walsh wrote:
Hi,
I have the most peculiar problem (at least in my point of view) with
forwarding with jkmount. JkMount has always worked on my server, but
suddenly, without changing anything but the mod_jk settings (adding a
new jkmount and some rewriterules), JkMount
Hi,
I have the most peculiar problem (at least in my point of view) with
forwarding with jkmount. JkMount has always worked on my server, but
suddenly, without changing anything but the mod_jk settings (adding a
new jkmount and some rewriterules), JkMount suddenly only works if I
connect
it is the latter)
The situation is the following:
Currently we have several web applications running on a Tomcat 6 server.
For the sake of this explanation I will call then web1 and web2.
I have apache set up to use jkmount to forward requests from the apache
server to the tomcat server
to use jkmount to forward requests from the apache
server to the tomcat server. The problem is that I can only get apache
to forward things like www.esat.kuleuven.be/web1 and
www.esat.kuleuven.be/web2.
I would like to be able to forward things like
www.esat.kuleuven.be//somefancyname//web1
-trivial :)
The situation is the following:
Currently we have several web applications running on a Tomcat 6 server.
For the sake of this explanation I will call then web1 and web2.
I have apache set up to use jkmount to forward requests from the apache
server to the tomcat server
Hi Rainer,
I have been playing around with mod_rewrite, but as far as I can tell
the rewrite is done before the jkmount. So I can get this wonderful url
to be rewritten to the actual name of the web application, but since the
old and the new versions have the same name it will not work
Edwin Walsh wrote:
Hi Rainer,
I have been playing around with mod_rewrite, but as far as I can tell
the rewrite is done before the jkmount. So I can get this wonderful url
to be rewritten to the actual name of the web application, but since the
old and the new versions have the same name
I'm not sure whether this is the best mailing list for the question,
feel free to blame me if it isn't.
I have a simple configuration with apache 2.2.6, mod_jk 1.2.25 and
tomcat 6.0.14.
In tomcat I have a web application running, say /myapp, that I want to
publish in apache as the root
Carlo Montanari wrote:
I'm not sure whether this is the best mailing list for the question,
feel free to blame me if it isn't.
I have a simple configuration with apache 2.2.6, mod_jk 1.2.25 and
tomcat 6.0.14.
In tomcat I have a web application running, say /myapp, that I want to
publish in
From: Carlo Montanari [mailto:[EMAIL PROTECTED]
Subject: JkMount changing webapp context
In other words, when the users ask for
http://www.myapphost.tld/, they should see the
content of http://localhost:8009/myapp/
For a Tomcat-only solution, define as many Host elements in server.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dale,
BuildSmart wrote:
You're shitting me, it can't be that simple, thank you, it works as
configured with my ajp13 worker.
Yes, it's that simple. Usually the only problem with mod_jk setup is
that people try to add too much complexity at once. I
-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
right now before
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
about it.
I've never had a problem with mod_jk. No complaints required from my
end. It's possible that mod_jk was written to support only virtual
hosts, and not JkMount options at the top-level. I'd be surprised at
this, but there's an easy workaround: use a global virtual host. In any
event, if you
possible that mod_jk was written to support only virtual
hosts, and not JkMount options at the top-level. I'd be surprised at
this, but there's an easy workaround: use a global virtual host. In
any
event, if you need this global capability (and it sounds like you do),
try asking for this capability
who are fault and you should bitch to them about it.
I've never had a problem with mod_jk. No complaints required from my
end. It's possible that mod_jk was written to support only virtual
hosts, and not JkMount options at the top-level. I'd be surprised at
this, but there's an easy workaround
[%a %b %d %H:%M:%S %Y]
JkMount /*.jsp ajp13
JkOptions +ForwardKeySize +ForwardURICompat
/IfModule
___
my workers.ajp13.properties contains:
___
ps=/
# Define 1 real worker using ajp13
worker.list=ajp13
by not accessible.
I can't pre-define the mount points for the subdirectories because I
don't know what they are in advance, there doesn't seem to be a way to
define access to Tomcat based on the file extension since it wont let
you assign a mount point without a leading /.
JkMount /*.jsp
point without a leading /.
JkMount /*.jsp myworker
would be perfectly valid. You can combine prefixes and suffixes.
If there are no rules at all (no known prefixes and no known
suffixes) then your URL space is weird and you can only use
JkMount /* myworker
and live with the consequences
to define access to Tomcat based on the file extension since it wont
let you assign a mount point without a leading /.
JkMount /*.jsp myworker
would be perfectly valid. You can combine prefixes and suffixes.
If there are no rules at all (no known prefixes and no known suffixes)
then your URL space
they are in advance, there doesn't
seem to be a way to define access to Tomcat based on the file
extension since it wont let you assign a mount point without a
leading /.
JkMount /*.jsp myworker
would be perfectly valid. You can combine prefixes and suffixes.
If there are no rules at all (no known
Mayes schrieb:
Hi, all.
I seem to be having a bit of trouble with virtual hosts and mod_jk.
JkMount directives in a VirtualHost are ignored:
VirtualHost *
ServerName censea.cmayes.org
JkMount /* ajp13
ErrorLog /var/log/apache2/censea_error_log
TransferLog /var/log/apache2
of trouble with virtual hosts and mod_jk.
JkMount directives in a VirtualHost are ignored:
VirtualHost *
ServerName censea.cmayes.org
JkMount /* ajp13
ErrorLog /var/log/apache2/censea_error_log
TransferLog /var/log/apache2/censea_access_log
DocumentRoot /usr/local/www/
DirectoryIndex
initialized for the virtual server.
Could you please confirm, that the mappings you enter to the virtual
servers work, and the problem is only the misleading log lines?
Regards,
Rainer
Chris Mayes schrieb:
Hi, all.
I seem to be having a bit of trouble with virtual hosts and mod_jk.
JkMount directives
Hi, all.
I seem to be having a bit of trouble with virtual hosts and mod_jk.
JkMount directives in a VirtualHost are ignored:
VirtualHost *
ServerName censea.cmayes.org
JkMount /* ajp13
ErrorLog /var/log/apache2/censea_error_log
TransferLog /var/log/apache2/censea_access_log
Martin,
Indeed, I had the same setting with the standalone Tomcat webserver
and the configuration your mention would work properly as it expected.
As I had mentioned in earlier posts to this thread, I do not have a
reason to utilize a third party webserver. At this point I am just
trying various
the original
message without making a copy. Thank you.
- Original Message -
From: Evan J [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, August 21, 2006 9:28 AM
Subject: Re: JkMount and Context path
Martin,
Indeed, I had the same setting with the standalone
JkMount is used for the requests to be processes by
jk_mod and passed on to Tomcat? Allow me to restate my example, so you
will be able to answer my question through the example itself.
JkMount /*/esrvlt/* worker1
JkMount /*/esrvlt/*.jsp worker1
The web application is myapp
Context path is /someuri
Why are you mixing up Apache and Tomcat?
If you are speaking of AJP 'context' term
if you look at the doc you will see
JkMount [URL prefix] [Worker name]
/*where URL prefix is the context*/
JkMount /*/esrvlt/* worker1
Send all requests of whateverWebApp/eservlet/WhateverFileName to worker1 so
Yes, I understand that perfectly. What I am asking is what if we
include a web application Context path, that is Context
path=someuri Of course, JkMount /*/eservlet/* would relay all
the request with mywebapp/eservlet/* from Apache to Tomcat -- I am
aware of that. Now if we set Context path
Evan J wrote:
Yes, I understand that perfectly. What I am asking is what if we
include a web application Context path, that is Context
path=someuri Of course, JkMount /*/eservlet/* would relay all
the request with mywebapp/eservlet/* from Apache to Tomcat -- I am
aware of that. Now if we
flawlessly so
that's why I was asking whether specifying JkMount would have any
bearing on Context path which seems like it doesn't in this case.
Again, my configration is as following:
httpd.conf:
virtualhost ...
ServerName vh.host.com
DocumentRoot /path/to/www
JkMount /* worker1
JkMount /*.jsp
Evan J wrote:
conf/enginename/vh.host.com/myapp.xml:
Context path=someuri
docBase=/myapp...
Ahh. Light dawns. It wasn't clear (to me at least) that you were using
a context.xml file. I had assumed you were specifying the context
inside server.xml. Using the configuration above
I've a question regarding the way jk_mod relays requests to Tomcat
servlets. If I have set my virtualhost to supposedly send requests
with such JkMount directive URL prefix, /serve/* and /serve/*.jsp,
then I take it, the only way for jk_mod relays requests for this
virtualhost to Tomcat web
/*httpd.conf
JkMount maps all JSP (*.jsp) to ajp13
*/
e.g.
httpd.conf
JkMount /*.jsp ajp13
/*map ajp13 to your webapp docRoot /var/tomcat4/webapps/domain1
VirtualHost *
ServerName domain1.com
ServerAlias www.domain1.com
DocumentRoot /var/tomcat4/webapps/domain1
JkMount /* ajp13
When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this makes your new message appear as part
of the old thread.
A strange problem occured to me. This is a part of my httpd.conf:
VirtualHost *:81
ServerName hamsun
RewriteEngine on
RewriteRule ^/victoria - [L,PT]
RewriteRule (.*) /victoria$1 [L,PT]
JkMount/* hamsunworker
/VirtualHost
It actually works
Hello
What's about the directive NameVirtualHost in your httpd.conf ?
Jean-Claude
-Message d'origine-
De : Cedric Fontaine [mailto:[EMAIL PROTECTED]
Envoyé : mardi 28 février 2006 00:04
À : Tomcat Users List
Objet : Same jkmount, different server
Hello,
I'm trying to setup
Sangoi [mailto:[EMAIL PROTECTED]
Sent: Monday, October 31, 2005 5:49 PM
To: 'Tomcat Users List'
Subject: RE: JkMount
Hi,
I tried as follows
My workers.properties :
workers.java_home=/usr/j2se
ps=/
worker.list=test1,test2,test3,test4
## TEST1 CONNECTOR
worker.test1.port=
worker.test1.host
How can i JkMount same URI twice in httpd.conf with different worker
specified?
e.g. i want to mount /example/* twice using different worker name.
JkMount /example/* worker1
JkMount /example/* worker2
But this is not working. How should i configure to achieve my motto?
Regds,
Nehal
worker.test2.type=ajp13
worker.test2.lbfactor=1
## TEST3 CONNECTOR
worker.test3.port=
worker.test3.host=xxx.xxx.xxx.xxx
worker.test3.type=lb
worker.test3.sticky_session=1
worker.test3.balance_workers=test2
My httpd.conf :
JkMount /example/* test1
JkMount /test/* test2
But, my test2 itself
worker.test3.port=
worker.test3.host=xxx.xxx.xxx.xxx
You should remove the two lines above.
worker.test3.type=lb
worker.test3.sticky_session=1
worker.test3.balance_workers=test2
My httpd.conf :
JkMount /example/* test1
JkMount /test/* test2
But, my test2 itself is not loading
72 matches
Mail list logo
