> Hi Rainer/Simon - I've just had another look at this. With no
> application running (IOW, all Java processes killed), I see this
> behaviour:
Sorry, I was confused because I thought we're talking about files from
Tomcat and not from Apache/mod_jk.
Regards,
Simon
>
> #
Hi Rainer/Simon - I've just had another look at this. With no
application running (IOW, all Java processes killed), I see this behaviour:
# systemctl start apache2
This create a number of apache2 processes (generally 7). 2 new mod_jk
files are created, corresponding to the apache2 process
Hi,
> Hi - I'm running mod_jk with an Apache front-end, and I'm having an
> issue with the JkShmFile files.
>
> Every time Apache restarts mod_jk creates two new files
> (jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never
> cleaned up; the log directo
Hi there,
Am 19.12.23 um 18:05 schrieb EML:
Hi - I'm running mod_jk with an Apache front-end, and I'm having an
issue with the JkShmFile files.
Every time Apache restarts mod_jk creates two new files
(jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never
cleaned up; the log
Hi - I'm running mod_jk with an Apache front-end, and I'm having an
issue with the JkShmFile files.
Every time Apache restarts mod_jk creates two new files
(jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never
cleaned up; the log directory simply fills up with these files
CVE-2023-41081 Apache Tomcat Connectors (mod_jk) Authentication Bypass
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
- Apache Tomcat Connectors mod_jk Connector 1.2.0 to 1.2.48
Description:
In some circumstances, such as when a configuration included
"JkOp
CVE-2023-41081 Apache Tomcat Connectors (mod_jk) Authentication Bypass
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
- Apache Tomcat Connectors mod_jk Connector 1.2.0 to 1.2.48
Description:
In some circumstances, such as when a configuration included
"JkOp
CVE-2023-41081 Apache Tomcat Connectors (mod_jk) Information Disclosure
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
- Apache Tomcat Connectors mod_jk Connector 1.2.0 to 1.2.48
Description:
In some circumstances, such as when a configuration included
Martin,
On 7/3/23 04:47, Martin Knoblauch wrote:
On 6/29/23 17:06, Rainer Jung wrote:
Since I try to push people into mod_proxy, I am hesitant to implement
more and more features which keep people from switching ;)
Hi Rainer,
so, what do you suggest for the mod_jk retirement
rs@tomcat.apache.org
Subject: Re: [mod_jk] Is it possible to set the value of a specific attribute
via
HTTP?
Rainer,
On 6/29/23 17:06, Rainer Jung wrote:
Hi Chris,
Am 29.06.23 um 15:00 schrieb Christopher Schultz:
All,
I've been using mod_jk forever and have some tools[1][2] to check on
th
On 6/29/23 17:06, Rainer Jung wrote:
>
> > Since I try to push people into mod_proxy, I am hesitant to implement
> > more and more features which keep people from switching ;)
>
>
Hi Rainer,
so, what do you suggest for the mod_jk retirement?
mod_proxy+mod_proxy_ajp, or ju
nal Message-
> From: Christopher Schultz
> Sent: Friday, June 30, 2023 2:19 PM
> To: users@tomcat.apache.org
> Subject: Re: [mod_jk] Is it possible to set the value of a specific attribute
> via
> HTTP?
>
> Rainer,
>
> On 6/29/23 17:06, Rainer Jung wrote:
> >
Rainer,
On 6/29/23 17:06, Rainer Jung wrote:
Hi Chris,
Am 29.06.23 um 15:00 schrieb Christopher Schultz:
All,
I've been using mod_jk forever and have some tools[1][2] to check on
the status of a worker and change its state using the status worker.
One of the samples I check is the "e
Hi Chris,
Am 29.06.23 um 15:00 schrieb Christopher Schultz:
All,
I've been using mod_jk forever and have some tools[1][2] to check on the
status of a worker and change its state using the status worker.
One of the samples I check is the "errors" count and if it's above 0
the
All,
I've been using mod_jk forever and have some tools[1][2] to check on the
status of a worker and change its state using the status worker.
One of the samples I check is the "errors" count and if it's above 0
then I report an error to my monitoring system.
The problem is that
mod_jk thrash by just requesting pages that didn't
exist. It's not a huge issue for us since most of our apps are
authenticated using SAML, so all requests are intercepted before the
request is ever sent to Tomcat, but for our apps that don't require
authentication, it would be easy to exploit any app
at the time would recommend
adding 404 to the fail_on_status, which is what we did...until I
realized that we were causing our own internal DOS attack when we had
a 404 mistakenly left in our apps; that got me thinking how easy it
would be to make mod_jk thrash by just requesting pages that didn't
exist
Dan,
On 6/20/23 11:32, Dan McLaughlin wrote:
When I attach with a debugger, I can see what's causing it not to
work. When the Web Application is started, then
request.getContext(); returns the correct Web Application context, but
when the application is stopped, request.getContext(); returns
ng I just tested was to undeploy the ROOT context, which is how
> we run anyways, and this causes request.getContext() to return null,
> which with the code, as is, results in a null pointer and a 500 being
> thrown--which inadvertently would cause mod_jk to retry on another
> node. I don't
One thing I just tested was to undeploy the ROOT context, which is how
we run anyways, and this causes request.getContext() to return null,
which with the code, as is, results in a null pointer and a 500 being
thrown--which inadvertently would cause mod_jk to retry on another
node. I don't like
to the fail_on_status, which is what we did...until I
realized that we were causing our own internal DOS attack when we had
a 404 mistakenly left in our apps; that got me thinking how easy it
would be to make mod_jk thrash by just requesting pages that didn't
exist. It's not a huge issue for us since most
We typically don't deploy a ROOT context in our production
environments--for no other reason than making it more difficult to poke
around. I'll look at that as an option. Thanks for the tips.
--
Thanks,
Dan
On Tue, Jun 20, 2023 at 10:28 AM Mark Thomas wrote:
> On 20/06/2023 15:41, Dan
When I attach with a debugger, I can see what's causing it not to
work. When the Web Application is started, then
request.getContext(); returns the correct Web Application context, but
when the application is stopped, request.getContext(); returns the
ROOT context, which is up, so the 404 is
On 20/06/2023 15:41, Dan McLaughlin wrote:
So I tried to create a Valve to check to see if the application is stopped
and convert the 404 response to a 503, but I haven't had any luck getting
it to work. Is there another internal API that I should be using?
context.getState().isAvailable
ways
So I tried to create a Valve to check to see if the application is stopped
and convert the 404 response to a 503, but I haven't had any luck getting
it to work. Is there another internal API that I should be using?
context.getState().isAvailable
ways seems to report the app is available even
, so it's not a huge issue, and even more rarely
do we run into issues in production where we need to stop just one app, but
it has happened. It would just be nice not to have to go tell mod_jk that a
node was down for an application or have to stop Tomcat to get it to not
send requests to a stopped
On 14/06/2023 19:49, Dan McLaughlin wrote:
Hello,
This is probably a question that would be better suited for the dev list,
but I thought I'd start here first.
That depends. It is generally better to start on the users list.
Does anyone understand the reasoning behind why Tomcat, when
to configure mod_jk
fail_on_status to failover for 404s. 3) Lastly, configuring mod_jk to
failover for 404s means you will never throw a 404 even when all apps are
started, but a page really doesn't exist. 4) It seems to fail over for
every 404 would make it very easy to create a DOS attack causing
-Original Message-
From: Christopher Schultz
Sent: Wednesday, December 7, 2022 4:54 PM
To: Tomcat Users List ;
jonmcalexan...@wellsfargo.com.INVALID
Subject: Re: Mod_JK vs Mod_Proxy
Jon,
On 12/6/22 16:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
What, pray tell, is an encrypted AJP
> Sent: Wednesday, December 7, 2022 4:54 PM
> To: Tomcat Users List ;
> jonmcalexan...@wellsfargo.com.INVALID
> Subject: Re: Mod_JK vs Mod_Proxy
>
> Jon,
>
> On 12/6/22 16:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > What, pray tell, is an encrypted AJP connection?
Sent: Tuesday, December 6, 2022 3:01 PM
To: users@tomcat.apache.org
Subject: Re: Mod_JK vs Mod_Proxy
Jon,
On 12/6/22 12:36, jonmcalexan...@wellsfargo.com.INVALID wrote:
IMHO, switching to mod_proxy, and using it over SSL, is by far better than
using mod_jk or mod_ajp, primarily as mod_proxy
chultz
> Sent: Tuesday, December 6, 2022 3:01 PM
> To: users@tomcat.apache.org
> Subject: Re: Mod_JK vs Mod_Proxy
>
> Jon,
>
> On 12/6/22 12:36, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > IMHO, switching to mod_proxy, and using it over SSL, is by far better than
>
Jon,
On 12/6/22 12:36, jonmcalexan...@wellsfargo.com.INVALID wrote:
IMHO, switching to mod_proxy, and using it over SSL, is by far better than using mod_jk
or mod_ajp, primarily as mod_proxy allows for secure proxy connection, whereas mod_jk and
mod_ajp aren't "s
IMHO, switching to mod_proxy, and using it over SSL, is by far better than
using mod_jk or mod_ajp, primarily as mod_proxy allows for secure proxy
connection, whereas mod_jk and mod_ajp aren't "secure" as they are not
encrypted channels.
Again, just my .02 worth.
Dream * Excel
Mark,
On 12/6/22 08:48, Mark H. Wood wrote:
On Mon, Dec 05, 2022 at 03:37:59PM -0500, Christopher Schultz wrote:
On 12/5/22 15:03, Cathy Spears wrote:
Using Tomcat 8.5 and 9.0 with 32-bit Apache 2.4 and mod_jk. Are there
benefits to using mod_proxy instead of mod_jk? Also, is there a
planned
On Mon, Dec 05, 2022 at 03:37:59PM -0500, Christopher Schultz wrote:
> On 12/5/22 15:03, Cathy Spears wrote:
> > Using Tomcat 8.5 and 9.0 with 32-bit Apache 2.4 and mod_jk. Are there
> > benefits to using mod_proxy instead of mod_jk? Also, is there a
> > planned e
Cathy,
On 12/5/22 15:03, Cathy Spears wrote:
Using Tomcat 8.5 and 9.0 with 32-bit Apache 2.4 and mod_jk. Are there
benefits to using mod_proxy instead of mod_jk? Also, is there a
planned end of life for mod_jk or will it continue to be supported
for now?
Hopefully this will be helpful:
https
Using Tomcat 8.5 and 9.0 with 32-bit Apache 2.4 and mod_jk. Are there benefits
to using mod_proxy instead of mod_jk? Also, is there a planned end of life for
mod_jk or will it continue to be supported for now?
Thanks,
Cathy
DISCLAIMER:
The information transmitted in this e-mail message
Thanks Mark! Was looking on VS17 tab. All good.
From: Mark Thomas
Sent: Monday, December 5, 2022 6:10 AM
To: users@tomcat.apache.org
Subject: [External] Re: Looking for Mod_JK compiled for Windows
CAUTION: This email originated from an external system. Do not click links,
open attachments
On 05/12/2022 13:46, Cathy Spears wrote:
Hello all - I am looking for the latest version of mod_jk for Windows. At one
time I was able to find it on Apache Lounge but no longer. Please advise.
They are still there:
https://www.apachelounge.com/download/VS16/
Mark
Hello all - I am looking for the latest version of mod_jk for Windows. At one
time I was able to find it on Apache Lounge but no longer. Please advise.
Thanks,
Cathy
DISCLAIMER:
The information transmitted in this e-mail message and attachments, if any, may
be attorney-client information
Hi Chris,
Am 27.05.2022 um 01:49 schrieb Christopher Schultz:
On 5/26/22 17:25, Rainer Jung wrote:
Am 26.05.2022 um 21:49 schrieb Christopher Schultz:
Would you prefer to use mod_unique_id + unique-id-logging in mod_jk over
just adding more request-level information to the mod_jk.log? I'm
hink it would be better to try
to add a unique request ID as a correlation ID. Apache can already
generate them using mod_unique_id and you can add them there to the
access log.
Would you prefer to use mod_unique_id + unique-id-logging in mod_jk over
just adding more request-level information to
uest ID as a correlation ID. Apache can already
generate them using mod_unique_id and you can add them there to the
access log.
Now how could we make that ID accessible from mod_jk?
We could either add it as a new item to jk_ws_service and I think it
would be a good fit. Any server not yet prov
n in microseconds)
- remember that Apache logs start of request as default time stamp, but
mod_jk logs at the moment of error, so later than start of request.
Finding the right access log line for a mod_jk error log line now means:
- filter the access log according to the PID:TID logged in
All,
On 5/26/22 15:49, Christopher Schultz wrote:
Rainer,
On 5/16/22 13:48, Christopher Schultz wrote:
Rainer,
I've been looking into this a little more in my production environment.
These errors are not super common, but there seems to be a steady
trickle of errors from my two services
Can be done by using the %{format}t syntax in the
LogFormat and adding "usec_frac" to the format.
- adding %D to the access log format (duration in microseconds)
- remember that Apache logs start of request as default time stamp, but
mod_jk logs at the moment of error, so later th
Rainer,
On 5/16/22 13:48, Christopher Schultz wrote:
Rainer,
I've been looking into this a little more in my production environment.
These errors are not super common, but there seems to be a steady
trickle of errors from my two services that have human users. I see 0
errors for my
n 3/24/22 05:50, Rainer Jung wrote:
Hi Chris,
client errors in jk log are always errors occurring when mod_jk tries
to write back what it got from the backend using web server APIs to
the client of the web server (user, browser etc.). So they point to a
problem between and including the web ser
Rainer,
On 3/24/22 05:50, Rainer Jung wrote:
Hi Chris,
client errors in jk log are always errors occurring when mod_jk tries to
write back what it got from the backend using web server APIs to the
client of the web server (user, browser etc.). So they point to a
problem between
Hi Chris,
client errors in jk log are always errors occurring when mod_jk tries to
write back what it got from the backend using web server APIs to the
client of the web server (user, browser etc.). So they point to a
problem between and including the web server and something in front
r state" which looks like mod_jk is
considering this *worker* to be in an error-state, meaning that it would
direct traffic to another worker. I'm not seeing the worker being put
into an ERR state. Is that log message jus
All,
What kinds of things will cause a "client error" in mod_jk's accounting?
Does that mean things like unexpected disconnects on the part of the
remote client (i.e. web browser), or does it mean failure of the jk
module itself to connect (as a client) to the back-end Tomcat?
I'm starting
to an interference between Apache httpd and mod_jk.
For the full picture, the infrastructure setup contains
1. a Loadbalancer providing HTTPS, HTTP/1.1 and HTTP/2 for Clients.
2. an Apache httpd 2.4 webserver (HTTP only) with mod_jk
3. a Tomcat mit AJP-Connector
We have an application doing many different
Hello Stefan,
the debug output of mod_jk shows at least which route the request is going:
[info] jk_handler::mod_jk.c (2968): No body with status=401 for
worker=ajp13_worker
So it looks like that the code
https://github.com/apache/tomcat-connectors/blob/main/native/apache-2.0/mod_jk.c#L2954
Hello Stefan,
Now I got it. Thanks for the clarification :)
-Ursprüngliche Nachricht-
Von: Stefan Mayr
Gesendet: Dienstag, 15. Februar 2022 14:26
An: users@tomcat.apache.org
Betreff: Re: mod_jk interference with ErrorDocument/Alias on HEAD request
Hello Thomas,
Am 15.02.2022 um 11:38
Hello Thomas,
Am 15.02.2022 um 11:38 schrieb Thomas Hoffmann (Speed4Trade GmbH):
Hello Stefan,
by spec / RFC, a HEAD request is not allowed to return any body.
Greetings,
Thomas
This is true and that is why i'm writing to this list. In the described
case mod_jk returns a response body
Hello Stefan,
by spec / RFC, a HEAD request is not allowed to return any body.
Greetings,
Thomas
-Ursprüngliche Nachricht-
Von: Stefan Mayr
Gesendet: Montag, 14. Februar 2022 23:07
An: users@tomcat.apache.org
Betreff: Re: mod_jk interference with ErrorDocument/Alias on HEAD request
Hello again,
a self-compiled mod_jk 1.2.48 shows the same issue.
Am 13.02.2022 um 18:37 schrieb Stefan Mayr:
Hi,
looking at the source code
https://github.com/apache/tomcat-connectors/blob/main/native/apache-2.0/mod_jk.c#L2954#L2973
I did some more testing:
Variant 1: JkMount /demo
gs,
Thomas
-Ursprüngliche Nachricht-
Von: Stefan Mayr
Gesendet: Sonntag, 13. Februar 2022 18:37
An: users@tomcat.apache.org
Betreff: Re: mod_jk interference with ErrorDocument/Alias on HEAD request
Hi,
looking at the source code
https://github.com/apache/tomcat-connectors/blob/main/native/
->status
The response only seems correct for variant 1 - which is configured to
let Apache httpd handle all responses for status codes >= 401. For
variant 2 mod_jk seems to handle the response itself - contrary to what
the comment explains.
Am 12.02.2022 um 14:24 schrieb Stefan Mayr:
t /error/* ajp13_worker
-Ursprüngliche Nachricht-
Von: Stefan Mayr
Gesendet: Samstag, 12. Februar 2022 14:24
An: Tomcat Users List
Betreff: mod_jk interference with ErrorDocument/Alias on HEAD request
Hello Tomcat users,
this week we were debugging a strange connection iss
bug:
JkLogLevel
(same reference page as above).
Greetings,
Thomas
-Ursprüngliche Nachricht-
Von: Stefan Mayr
Gesendet: Samstag, 12. Februar 2022 14:24
An: Tomcat Users List
Betreff: mod_jk interference with ErrorDocument/Alias on HEAD request
Hello Tomcat users,
this week we were debugg
Hello Tomcat users,
this week we were debugging a strange connection issue which I tracked
down to an interference between Apache httpd and mod_jk.
For the full picture, the infrastructure setup contains
1. a Loadbalancer providing HTTPS, HTTP/1.1 and HTTP/2 for Clients.
2. an Apache httpd
Brian,
On 10/28/20 21:24, Paquin, Brian wrote:
Chris,
On Oct 27, 2020, at 12:31 PM, Christopher Schultz
wrote:
Brian
On 10/26/20 15:33, Paquin, Brian wrote:
I’m trying to build httpd and mod_jk for the first time on a macOS 10.15.7 box.
XCode 12.1 is installed and I was able to compile
Chris,
> On Oct 27, 2020, at 12:31 PM, Christopher Schultz
> wrote:
>
> Brian
>
> On 10/26/20 15:33, Paquin, Brian wrote:
>> I’m trying to build httpd and mod_jk for the first time on a macOS 10.15.7
>> box. XCode 12.1 is installed and I was able to compile Ope
Brian
On 10/26/20 15:33, Paquin, Brian wrote:
I’m trying to build httpd and mod_jk for the first time on a macOS 10.15.7 box.
XCode 12.1 is installed and I was able to compile OpenSSL 1.1.1g.
I got an error “Can not determine the proper size for pid_t” when compiling
httpd (v2.4.46
I’m trying to build httpd and mod_jk for the first time on a macOS 10.15.7 box.
XCode 12.1 is installed and I was able to compile OpenSSL 1.1.1g.
I got an error “Can not determine the proper size for pid_t” when compiling
httpd (v2.4.46) with included apr (v1.7.0).
This issue https
@Klaus Trachtler:
Managed to build mod_jk RPM for CentOS8.
See https://gist.github.com/robertoschwald/3317b4d777f44260fef86c5059955ffc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/18/20 18:29, Jerry Malcolm wrote:
> I'm taking Christopher's advice to remove httpd and mod_jk out of
> my process and go straight to Tomcat on port 80. At this point the
> only thing I've done is stop the httpd service a
I'm taking Christopher's advice to remove httpd and mod_jk out of my
process and go straight to Tomcat on port 80. At this point the only
thing I've done is stop the httpd service and change the Connector port
to 80. I'm running on my local machine. I have a hosts entry set
Hi Klaus,
Am 06.07.2020 um 15:13 schrieb Klaus Tachtler:
> Hi,
>
> I'm trying to build a rpm package for CentOS-8 for mod_jk with the
> latest version 1.2.48. While building the rpm package, following error
> occurs:
>
>
> - %< -
>
> ...
> make[1]:
an environment that has the potential for a
>>>> large number of simultaneous requests coming in. I have a
>>>> basic Apache HTTPD with mod_jk talking to Tomcat, all on the
>>>> same Amazon EC2 instance. From my understanding, I have the
>>>> poten
-
Hash: SHA256
Jerry,
On 7/7/20 16:50, Jerry Malcolm wrote:
I'm setting up an environment that has the potential for a large
number of simultaneous requests coming in. I have a basic Apache
HTTPD with mod_jk talking to Tomcat, all on the same Amazon EC2
instance. From my understanding, I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/7/20 16:50, Jerry Malcolm wrote:
> I'm setting up an environment that has the potential for a large
> number of simultaneous requests coming in. I have a basic Apache
> HTTPD with mod_jk talking to Tomcat, all on the same A
I'm setting up an environment that has the potential for a large number
of simultaneous requests coming in. I have a basic Apache HTTPD with
mod_jk talking to Tomcat, all on the same Amazon EC2 instance. From my
understanding, I have the potential of maxing out connections at httpd
Hi,
I'm trying to build a rpm package for CentOS-8 for mod_jk with the
latest version 1.2.48. While building the rpm package, following error
occurs:
- %< -
...
make[1]: Entering directory
'/root/rpmbuild/BUILD/tomcat-connectors-1.2.48-src/native/apache-2.0'
/usr/lib64/ap
Il giorno ven, 29/05/2020 alle 14.09 -0400, Christopher Schultz ha
scritto:
> Giuseppe,
>
> On 5/29/20 11:57, Giuseppe Sacco wrote:
> > [...]
> > misconfigured machines and failed with 404 errors. From what I
> > understood, the mod_jk protocol only allows to c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 5/29/20 11:57, Giuseppe Sacco wrote:
> Hello,I have an apache httpd with mod_jk that load balance
> requests among two different tomcat servers.Today, one of the
> tomcat servers has been rebooted and tomcat could n
Hello,I have an apache httpd with mod_jk that load balance requests
among two different tomcat servers.Today, one of the tomcat servers has
been rebooted and tomcat could not deploy the application since it
failed to find a configuration file. Please note that tomcat was
running correctly, only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas,
On 3/4/20 19:37, Thomas Glanzmann wrote:
> allowedRequestAttributesPattern=JK_LB_ACTIVATION
Note that JK_LB_ACTIVATION is already in the list of white-listed
attribute names. You should probably not have to set this
configuration
On 06/03/2020 06:46, Thomas Glanzmann wrote:
> the issue seems to be that mod_jk no longer works without a password
> with tomcat7. So you need to set a password on both sites, and than
> everything works again.
This is not the case. Tomcat can be configured so a secret is not
sion of Tomcat.
the issue seems to be that mod_jk no longer works without a password
with tomcat7. So you need to set a password on both sites, and than
everything works again.
server.xml:
workers.properties of mod_jk
worker.tomcat-06.secret=verysecure
If I do _not_ set a password I'm getting a
ill facing the same problem with 403. Might it be possible that I need
> to use a secret in order to access ajp from mod_jk?
>
If you don't set secretRequired="false" properly then at start time Tomcat
will complain if there is no specified "secret" attribute.
If it doesn't compla
Hello Martin,
> > This should be: secretRequired="false".
> > This attribute has been renamed recently.
I just looked at my notes, and I tried that already yesterday night.
Still facing the same problem with 403. Might it be possible that I need
to use a secret in order to
Hello Martin,
> This should be: secretRequired="false".
> This attribute has been renamed recently.
thanks. I'll test later and let you know how it went.
Cheers,
Thomas
-
To unsubscribe, e-mail:
ealm.LockOutRealm">
> className="org.apache.catalina.realm.UserDatabaseRealm"
> resourceName="UserDatabase"/>
>
> unpackWARs="true" autoDeploy="true">
>
.
However when I try to access this using mod_jk, I get a 403. I used a sniffer
and it is coming from the AJP connector
Hello,
I've just upgraded to tomcat7 (7.0.100) afterwards I'm unable to
reconfigure it to the pre 7.0.100 behaviour where AJP connector listens
on the public ip address in order to use it with mod_jk. Can someone
help me out to make it works again? My server.xml
Am 25.04.2019 um 06:22 schrieb John Larsen:
Hello,
Is there a limit to the number of workers instances mod_jk can handle?
There will be limits due to general file descriptor limits, each TCP
connection counts as a file descriptor. But I am not aware of a limit on
the number of workers per
Hello,
Is there a limit to the number of workers instances mod_jk can handle?
I currently have 38 tomcat instances running on a machine. I have had up to
75 in the past, but this machine I keep getting bind exception errors but
lsof -i :port comes up empty when that particular tomcat is offline
Sent: 06 February 2019 06:41 PM
To: Tomcat Users List ; Rathore, Rajendra
Subject: Re: loss of connection with mod_jk(tomcat connector)
External email from: rainer.j...@kippdata.de
Hi Rajendra,
Am 06.02.2019 um 12:36 schrieb Rathore, Rajendra:
> Hi Mark,
>
> I am stuck and due
/show_bug.cgi?id=63075
but there is no progress on it.
as Mark already wrote, your mod_jk log file shows, that many of your
tomcat instances are down.
You have configured a load balancer with 9 members, listening on
localhost ports 8010-8018, but of these 9 tomcat instances only the one
listening
,
Rajendra Rathore
9922701491
-Original Message-
From: Rathore, Rajendra
Sent: 17 January 2019 10:33 AM
To: Tomcat Users List
Subject: RE: loss of connection with mod_jk(tomcat connector)
External email from: users-return-266670-rarathore=ptc@tomcat.apache.org
Hi Mark,
We configure
to enable extra loggers that will
help out to understand the problem better,
Thanks and Regards,
Rajendra Rathore
9922701491
-Original Message-
From: Mark Thomas
Sent: 17 January 2019 05:05 AM
To: Tomcat Users List
Subject: Re: loss of connection with mod_jk(tomcat connector)
External
On 16/01/2019 12:26, Rathore, Rajendra wrote:
> Hi Team,
>
>
>
> we are using Apache Http server with basic authentication, when we try
> to send some request to apache for authentication it will fail with 401
> error and when we check the JK Status,
>
> we found that status was not proper
Greetings all.
I'm trying to use mod_jk within a Docker container using the Alpine Linux
base. I was successful on building the Module, but when I activate it,
Apache gives me an instant Segmentation Fault.
Don't know if something is missing.
Right now, this is my Dockerfile:
https
remind us of the versions of Java and tomcat please, it will save us a search through
the archive.)
What I suppose is that you now have this configuration, on one host for httpd
and tomcat :
browser <- HTTP/S -> httpd + mod_jk <- AJP ->
> at the positions
> mentioned in the appBase/docBase attributes.
> If any of these overlap, you have a problem. It is not a fatal problem,
> and one can avoid
> the problem with a careful httpd configuration. But if there is an
> overlap, you are always
> at risk of forgetting t
xy_fcgi_module (shared)
> > proxy_fdpass_module (shared) proxy_ftp_module (shared)
> > proxy_http_module (shared) proxy_scgi_module (shared)
> > proxy_wstunnel_module (shared) ssl_module (shared) systemd_module
> > (shared) cgi_module (shared)
>
> That's like ... every
1 - 100 of 4151 matches
Mail list logo
