-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/26/15 8:05 PM, Chris Arnold wrote:
Yeah, that document is evidently a pack of lies. Specifically,
the path and docbase attributes in Context are ignored
in META-INF/context.xml files, and you really shouldn't have
your Context
I'm surprised that the Alfresco team is still giving-out advice that
was appropriate in the mid-2000s.
Some notes:
1. Don't put Context in server.xml. Just don't.
2. debug hasn't been used in ... forever.
3. path= is bad, and isn't necessary if you follow #1
It did not work so i took it out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/25/15 7:38 PM, Chris Arnold wrote:
If you won't re-name the web application, I think redirects will
be your best bet. If a client requests
http(s)://share2.domain.tld/, you should redirect them to
https://share2.domain.tld/share/
The best possible setup here is to set up httpd with more than one
VirtualHost (and SNI, since you are using HTTPS) with the correct
hostnames, etc., and only use JkMount from the share2 VirtualHost.
Then, re-name your application from share.war to ROOT.war and
re-deploy it into Tomcat. Use
If the application can't handle that (try it!), you'll have to make
other arrangements.
According to:
https://wiki.alfresco.com/wiki/Deploying_To_Server
that is not even necessary. I understand that link is a years old and talks
about tomcat 6 but the general idea is the same. I will try to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/26/15 4:52 PM, Chris Arnold wrote:
The best possible setup here is to set up httpd with more than
one VirtualHost (and SNI, since you are using HTTPS) with the
correct hostnames, etc., and only use JkMount from the share2
Yeah, that document is evidently a pack of lies. Specifically,
the path and docbase attributes in Context are ignored in
META-INF/context.xml files, and you really shouldn't have your
Context anywhere else (except in
conf/[engine]/[host]/[appname].xml, which behaves almost the same
way).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/26/15 5:36 PM, Chris Arnold wrote:
Yeah, that document is evidently a pack of lies. Specifically,
the path and docbase attributes in Context are ignored in
META-INF/context.xml files, and you really shouldn't have your
Context
Yeah, that document is evidently a pack of lies. Specifically, the
path and docbase attributes in Context are ignored in
META-INF/context.xml files, and you really shouldn't have your
Context anywhere else (except in conf/[engine]/[host]/[appname].xml,
which behaves almost the same way).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/23/15 7:49 PM, Chris Arnold wrote:
*sigh*
If you only want to proxy for one VirtualHost, then only set up
JkMounts in that one VirtualHost.
Like this:
VirtualHost *:80 ServerName share2..xxx
JkMount /* worker1 (or
If you won't re-name the web application, I think redirects will be
your best bet. If a client requests http(s)://share2.domain.tld/, you
should redirect them to https://share2.domain.tld/share/ and then
JkMount /share/* worker1. You can redirect using RedirectPermanant
or a few other things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/23/15 10:40 AM, Chris Arnold wrote:
What you want is:
JkMount /share2/* worker1
or maybe:
JkMount /share2/* balancer
workers.properties defines the workers (target host/port,
connection options, etc.) and the JkMount
*sigh*
If you only want to proxy for one VirtualHost, then only set up
JkMounts in that one VirtualHost.
Like this:
VirtualHost *:80
ServerName share2..xxx
JkMount /* worker1 (or balancer, whichever you want)
/VirtualHost
Maybe I wasn't clear in my other reply, the
What you want is:
JkMount /share2/* worker1
or maybe:
JkMount /share2/* balancer
workers.properties defines the workers (target host/port, connection
options, etc.) and the JkMount directives in httpd.conf map URL
patterns to those workers.
So JkMount /* proxied everything and we only need
What you want is:
JkMount /share2/* worker1
or maybe:
JkMount /share2/* balancer
workers.properties defines the workers (target host/port, connection
options, etc.) and the JkMount directives in httpd.conf map URL
patterns to those workers.
So JkMount /* proxied everything and we only need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/21/15 6:41 PM, Chris Arnold wrote:
Chris,
On 1/21/15 5:56 PM, Chris wrote: You must have changed something
since your original configuration. Do you have JkMount ajp13
somewhere? You need to use the worker name and not the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/21/15 5:56 PM, Chris Arnold wrote:
When i look at the apache log for that request, i dont see
where the request is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot,
+1
And also, could you specify again what URL you are requesting in the browser,
which you
would expect to be proxied to Tomcat ?
https://share2.domain.tld
Looking at the log you just showed, it seemed that the only requests ever
passed through
mod_jk for evaluation, where things like
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 1/21/15 5:56 PM, Chris Arnold wrote:
When i look at the apache log for that request, i dont see
where the request is even making it to apache or tomcat.
Try to request a static file from DocumentRoot
Chris,
On 1/21/15 5:56 PM, Chris wrote:
You must have changed something since your original configuration. Do
you have JkMount ajp13 somewhere? You need to use the worker name
and not the protocol name.
Can you post your updated workers.properties file, and related
httpd.conf configurations?
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
Am 22.01.2015 um 01:03 schrieb Chris Arnold:
+1
And also, could you specify again what URL you are requesting in the browser,
which you
would expect to be proxied to Tomcat ?
https://share2.domain.tld
Looking at the log you just showed, it seemed that the only requests ever
passed through
2015-01-17 2:31 GMT+03:00 Chris Arnold carn...@electrichendrix.com:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco
5.0.c which includes tomact 7.x i believe. SLES 11 has apache
Am 17.01.2015 um 00:31 schrieb Chris Arnold:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c which
includes tomact 7.x i believe. SLES 11 has apache 2.2.10. SLES 12 has
No JkMount?
mod_jk uses the JkMount directive to decide, which requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is used in your
Apache web server config to serve the requests for /myapp.
When i look at the existing
Am 17.01.2015 um 01:51 schrieb Konstantin Kolinko:
2015-01-17 2:31 GMT+03:00 Chris Arnold carn...@electrichendrix.com:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c which
Am 17.01.2015 um 03:43 schrieb Chris Arnold:
No JkMount?
mod_jk uses the JkMount directive to decide, which requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is used in your
Apache web server config to serve the
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
Am 17.01.2015 um 04:05 schrieb Chris Arnold:
When i look at the apache log for that request, i dont see where the request is
even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/share/
RewriteRule ^/(.*) https://share.domain.tld:8443/share/ [P]
That will forward any
I have the following configuration (config files below) and am
encountering the error
“ajp_connection_tcp_get_message::jk_ajp_common.c (1033): wrong
message format 0x4854 from 127.0.0.1:8082” when attempting to access
a URL that matches one of my JKMounted entries. My versions are
listed
[EMAIL PROTECTED] schrieb:
I have the following configuration (config files below) and am
encountering the error
“ajp_connection_tcp_get_message::jk_ajp_common.c (1033): wrong
message format 0x4854 from 127.0.0.1:8082” when attempting to access
a URL that matches one of my JKMounted
I have the following configuration (config files below) and am
encountering the error
âajp_connection_tcp_get_message::jk_ajp_common.c (1033): wrong
message format 0x4854 from 127.0.0.1:8082â when attempting to access
a URL that matches one of my JKMounted entries. My versions are
listed
On 16 Jul 2008 at 13:41, Vinod Nagarajan wrote:
Date sent: Wed, 16 Jul 2008 13:41:09 -0700
From: Vinod Nagarajan [EMAIL PROTECTED]
Subject:mod_jk configuration issue
To: users@tomcat.apache.org
Send reply to: Tomcat Users List users@tomcat.apache.org
Hi,
I am kind of new
What's your idea why you configured a socket timeout of 2?
nuka schrieb:
Hello,
I am facing to a problem concerning apache-tomcat configuration via mod_jk
for our production environment. We are using Apache: 2.0.55, Tomcat 5.0,
mod_jk 1.2.15.
Our first problem has been raised some weeks
Christopher Schultz-2 wrote:
Bruno,
Alias /jsp-examples /srv/www/tomcat5/base/webapps/jsp-examples
JkMount /jsp-examples/*.jsp ajp13
JkMount /jsp-examples/j_security_check ajp13
These three ought to do the trick. Which files aren't being served by
Apache httpd?
Well
Now I have an even stranger behavior...
I can only JkMount /jsp-examples, I did the same to /tomcat-docs,
/servlets-examples and /cocoon and I get :
Forbidden
You don't have permission to access /tomcat-docs/ on this server.
Additionally, a 403 Forbidden error was encountered while trying to
Bruno,
Now I have an even stranger behavior...
I can only JkMount /jsp-examples, I did the same to /tomcat-docs,
/servlets-examples and /cocoon and I get :
Forbidden
You don't have permission to access /tomcat-docs/ on this server.
Additionally, a 403 Forbidden error was encountered
Christopher Schultz-2 wrote:
Here's my /etc/apache2/conf.d/jk.conf:
http://www.nabble.com/file/3921/jk.conf jk.conf
(These are never coming through. How are you trying to attach files?)
I'm using Upload File... option. Here's a copy/paste:
# simple configuration for apache (for AJP
Bruno,
bcochofel wrote:
Christopher Schultz-2 wrote:
Here's my /etc/apache2/conf.d/jk.conf:
http://www.nabble.com/file/3921/jk.conf jk.conf
(These are never coming through. How are you trying to attach files?)
I'm using Upload File... option.
Hmm... I didn't know that one could upload
Christopher Schultz-2 wrote:
Hmm... I didn't know that one could upload file to an email...
consider using copy/paste in the future. It seems to have worked, here.
I'm using www.nabble.com...
Christopher Schultz-2 wrote:
### jps-examples ##
Bruno,
Hmm... I didn't know that one could upload file to an email...
consider using copy/paste in the future. It seems to have worked, here.
I'm using www.nabble.com...
Ah. I think the list will clip-out attachments. I'm not sure of the
rules, but copy/paste pretty much always works.
Bruno,
when I try
http://localhost/jsp-examples http://localhost/jsp-examples (without the /)
I get this error:
Forbidden
You don't have permission to access /jsp-examples on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an
ErrorDocument to handle
Hi,
Christopher Schultz wrote:
Bruno,
when I try
http://localhost/jsp-examples http://localhost/jsp-examples (without the /)
I get this error:
Forbidden
You don't have permission to access /jsp-examples on this server.
Additionally, a 403 Forbidden error was encountered while trying to
Well I've tried adding DirectoryIndex index.html index.htm index.jsp but no
good...
My Apache configuration has this and all the links work with or without the
/
Does jk.cong overrides my apache conf?
Christopher Schultz-2 wrote:
Bruno,
when I try
http://localhost/jsp-examples
Well I would appreciated...
Jorge Cabrera wrote:
Hi,
Christopher Schultz wrote:
Bruno,
when I try
http://localhost/jsp-examples http://localhost/jsp-examples (without
the /)
I get this error:
Forbidden
You don't have permission to access /jsp-examples on this server.
Sent: Monday, October 30, 2006 10:19 AM
Subject: Re: mod_jk configuration
Well I've tried adding DirectoryIndex index.html index.htm index.jsp but no
good...
My Apache configuration has this and all the links work with or without the
/
Does jk.cong overrides my apache conf?
Christopher
I had
JkMount /jsp-examples worker1
and now the problem is gone... Thanks
I have one more question, let's take /jsp-examples to explain...
I want *.jsp send to tomcat for processing but all static contents processed
by apache, how can I do this?
Sorry for all the question but I'm new
Bruno,
Well I've tried adding DirectoryIndex index.html index.htm index.jsp but no
good...
Can you post the relevant portions of your httpd.conf?
Does jk.cong overrides my apache conf?
jk.conf is just included in httpd.conf (right?), so it can certainly
override your httpd.conf.
-chris
Bruno,
I have one more question, let's take /jsp-examples to explain...
I want *.jsp send to tomcat for processing but all static contents processed
by apache, how can I do this?
This should be the default. Anything for which you do not explicitly
have a JkMount directive will be served by
But when I use JkMount /jsp-examples ajp13 doesn't this tell Apache that
everything inside /jsp-examples goes to Tomcat?
Christopher Schultz-2 wrote:
Bruno,
I have one more question, let's take /jsp-examples to explain...
I want *.jsp send to tomcat for processing but all static
Bruno,
But when I use JkMount /jsp-examples ajp13 doesn't this tell Apache that
everything inside /jsp-examples goes to Tomcat?
No, it doesn't. JkMount does two kinds of matching: exact and wildcard.
Exact:
JkMount /jsp-examples ajp13
This will map the URI /jsp-examples to Tomcat, and NO
Well I tried that but no good... I'vre tried this and still nothing:
# The following line makes apache aware of the location of
# the /jsp-examples context
Alias /jsp-examples /srv/www/tomcat5/base/webapps/jsp-examples
Directory /srv/www/tomcat5/base/webapps/jsp-examples
Bruno,
Alias /jsp-examples /srv/www/tomcat5/base/webapps/jsp-examples
JkMount /jsp-examples/*.jsp ajp13
JkMount /jsp-examples/j_security_check ajp13
These three ought to do the trick. Which files aren't being served by
Apache httpd?
Can you give an example of a URI that should
I did mod_jk2 with Virtual Host, and while its not the same I think that
doing VH will not be a problem once you get an idea of how it should/can be
setup.
THIS IS PSEUDO, DO NOT TAKE AS GOSPEL TRUTH !!! NO SUPPORT! :p
-- workers.properties file --
# Setting Tomcat Java Home
Dan -
Thanks very much for all this - looks like it should work with mod_jk too!
I'll let you know how I get on.
Jon
-Original Message-
From: Didier McGillis [mailto:[EMAIL PROTECTED]
Sent: 26 January 2006 19:32
To: users@tomcat.apache.org
Subject: RE: mod_jk configuration directives
56 matches
Mail list logo
