rnal server (the LDAP server), it took quite a long
>> time to track down, as the web servers were in fact configured
>> identically :)
>
> Thanks for letting us know!
It's frustrating that there are no errors or warnings logged about
such things. You'd think "can&
the LDAP server), it took quite a long time to track down, as
the web servers were in fact configured identically :)
Thanks for letting us know!
Hopefully the status worker activation update problem in the other
thread will be fixed by a valid shm path. Otherwise analysis will get
nasty ..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 1/10/15 2:56 PM, Christopher Schultz wrote:
> I'm having a problem with mod_jk 1.2.40 under Apache 2.4.10. After
> a successful start up, accessing the mod_jk status page gives me a
> 500 error with no errors on the screen or in the logs.
S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm having a problem with mod_jk 1.2.40 under Apache 2.4.10. After a
successful start up, accessing the mod_jk status page gives me a 500
error with no errors on the screen or in the logs.
Here's what I see from a mod_jk trace log:
[Sat Jan 1
On 02.03.2013 15:52, Christopher Schultz wrote:
> All,
>
> Motivated by seeing Rainer's presentation at ApacheCon 2013,
> "Monitoring Apache Tomcat and the Apache Web" [1], I started looking
> at mod_jk's status worker - particularly the XML output as I believe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Motivated by seeing Rainer's presentation at ApacheCon 2013,
"Monitoring Apache Tomcat and the Apache Web" [1], I started looking
at mod_jk's status worker - particularly the XML output as I believe
it will be the easiest
On 25.10.2009 17:12, Mohit Anchlia wrote:
> Thanks. Is the JkShmfile something new? It worked when we had mod_jk
> 1.25. What is JkshmFile used for?
No it exists since a long time. The exact way of using it internally
changed a bit from version to version. Its main puposes are:
- providing statis
idn't work, see below.
>
>> Do you know how load balancing was working then if the status worker
>> wasn't running? During our perf test I did see that it was getting
>> load balanced.
>
> Each Apache process will be able to load balance for itself, but the
On 25.10.2009 16:00, Mohit Anchlia wrote:
> I think I got it. It was JkShmFile that was missing.
yes, and the default didn't work, see below.
> Do you know how load balancing was working then if the status worker
> wasn't running? During our perf test I did see that it
I think I got it. It was JkShmFile that was missing.
Do you know how load balancing was working then if the status worker
wasn't running? During our perf test I did see that it was getting
load balanced.
On Sun, Oct 25, 2009 at 7:50 AM, Mohit Anchlia wrote:
> mod_jk 1.27 came with the
t; On 25.10.2009 15:18, Mohit Anchlia wrote:
>> I posted this earlier to old thread. I am posting it with new thread.
>>
>> Apache 2.2.11, mod_jk/1.2.28:
>>
>> There seems to be a problem with activation of status worker JkStatus.
>> Even after explicitly sa
earlier to old thread. I am posting it with new thread.
>
> Apache 2.2.11, mod_jk/1.2.28:
>
> There seems to be a problem with activation of status worker JkStatus.
> Even after explicitly saying "stopped" for one of the workers the
> "Act" keeps going bac
I posted this earlier to old thread. I am posting it with new thread.
Apache 2.2.11, mod_jk/1.2.28:
There seems to be a problem with activation of status worker JkStatus.
Even after explicitly saying "stopped" for one of the workers the
"Act" keeps going back and forth. When
there is no way to write to workers.properties from within
mod_jk. There is also no way to reset configuration settings in the
sense, that we throw away all dynamic configuration changes (done via
the status worker) and again use the origin
Hi,
on
http://tomcat.apache.org/connectors-doc/reference/status.html
there is written
"reset: reset all runtime information for a load balancer or one of its
members."
So I thought, that means a reset to the file based workers.properties
configuration (that is active after restarting web serv
Thank you.
It was related with the virtual hosts and it Works now.
Regards,
Nuno
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: terça-feira, 1 de Abril de 2008 16:08
To: Tomcat Users List
Subject: Re: status worker
Nuno Manuel Martins wrote:
> Hi,
>
>
Nuno Manuel Martins wrote:
Hi,
I tried before to do as you said and it did not work. I guess this is because
when I make the request the one answering is Apache httpd and not Tomcat, and I
don't think httpd has any clue of what a status worker is.
Sure it has. It asks mod_jk and m
Hi,
I tried before to do as you said and it did not work. I guess this is because
when I make the request the one answering is Apache httpd and not Tomcat, and I
don't think httpd has any clue of what a status worker is.
I tried to simplify it with just these 3 lines:
worker.jkstatus
Nuno Manuel Martins wrote:
Hello,
I am new to tomcat in general and I am trying to setup jk_mod (using 1.2.25)
and I have already successfully installed it and put workers serving dynamic
content from the tomcat server with load balancing.
Now I wanted to setup the status worker to get some
Hello,
I am new to tomcat in general and I am trying to setup jk_mod (using 1.2.25)
and I have already successfully installed it and put workers serving dynamic
content from the tomcat server with load balancing.
Now I wanted to setup the status worker to get some statistics. I am using the
Hi,
I'm looking for a community member, who is willing to write a little
documentation about the status worker of mod_jk. We added a lot of new
information to it in the most recent release (candidate) 1.2.19 and I
think it would be worth writing a couple of lines about it. I can help
in answ
21 matches
Mail list logo
