Mladen Turk-3 wrote:
>
> Henk Fictorie wrote:
>> Hi,
>>
>> I think that I've been bitten by a resolved bug in mod_jk 1.2.27. The
>> changelog is describing this as:
>>
>> AJP13: Always send initial POST packet even if the client disconnected
&
my problem analysis correct
- Is this a regression bug
- Can I somehow circumvent this (other than not upgrading)
regards Henk Fictorie
--
View this message in context:
http://www.nabble.com/mod_jk-1.2.27-and-an-empty-POST-tp20699972p20699972.html
Sent from the Tomcat - User mailing list a
Brian.Horblit wrote:
>
>
> # Set w4 properties
> worker.w4.socket_keepalive=1
> worker.w4.socket_timeout=20
> worker.w4.reply_timeout=2
> worker.w4.retries=2
> worker.w4.connection_pool_timeout=60
> worker.w4.type=ajp13
> worker.w4.host=localhost
> worker.w4.port=8034
> worker.w4.lbfactor
l a sticky request for that
worker be routed to another worker or will the request fail?
regards Henk
Henk Fictorie wrote:
>
> Rainer,
>
> Thanks for your response.
> You mentioned our setting of retries=1, so I reread the documentation to
> find out that it actually means
ner Jung-3 wrote:
>
> Hi Henk,
>
> Henk Fictorie wrote:
>> Hi,
>>
>> We are using mod_jk 1.2.21 on Solaris 8. together Apache 2.0.59 with the
>> worker MPM.
>> We are moving our applicationserver to a new version which is also using
>> a
>> ne
ionTimeout on
the Tomcat side. Probably to some value > (connection_pool_timeout +
worker.maintain)??
Or should I set the connection_pool_minsize to match the minSpareThreads??
Or upgrade to mod_jk 1.2.25??
Advice is welcome.
regards Henk Fictorie
--
View this message in context:
http://w
orker lbworker are missing.
The URI mappings for the lbtestworker are displayed correct. I guess the
error has something to do with the fact that the lbworker is only JkMounted
for the virtualhost where the status worker is not mounted.
regards Henk Fictorie
--
View this message in context:
Mladen Turk wrote:
>
> Henk Fictorie wrote:
>> From reading the documentation I understand that connection_pool_size is
>> set
>> to its default value, the ThreadsPerChild setting from Apache.
>> According to the documentation the connection_pool_minsi
minimum size for the connection
pool and will all connections be freed (after the connection_pool_timeout
value)? Or will connections never be freed?
Does anyone know?
regards Henk Fictorie
--
View this message in context:
http://www.nabble.com/mod_jk---connection_pool_size-and-connection
ssion route jmv_web1
> * get_most_suitable_worker::jk_lb_worker.c (785): found best worker
> jvm_web2 (jvm_web2) using method 'Request'
>
> It seams the ruote is properly stetted by tomcat, but the loadbalancer
> choose the wrong worker.
>
> Matteo
>
> -Or
The session cookie is set to .jmv_web1 while your worker is set to
jvm_web2. I guess you've go jmv and jvm mixed up.
Henk
Matteo Turra wrote:
>
> I upgraded my apache+jk+tomcat configuration with new JK connector
> 1.2.20
>
>
>
> My system is one Apache http server and two tomcat runni
your
time.
regards Henk Fictorie
Rainer Jung-3 wrote:
>
> I requested this URL a few seconds ago, using
>
> curl -D - http://www.kpn.com/kpn/show/
>
> and it had the header
>
> Transfer-Encoding: chunked
>
> set. This somehow contradicts your first mail.
>
;t accept compressed responses. So responses
are sent uncompressed, but it still passes the mod_deflate filter.
regards Henk Fictorie
Rainer Jung-3 wrote:
>
> Hi Henk, do you have a simple app to reproduce the problem?
>
> Rainer Jung schrieb:
>> Hi Henk,
>>
>> I'
t;JkOptions +FlushPackets" cricumvent this behaviour.
- any ideas about the real cause of this problem.
Noticable:
In our response neither a 'Content-Length' or a 'Transfer-Encoding: chunked'
is send, could this be delaying sending the response to the browser?
regar
at
what moment and from which ip-adres the slow requests are coming. I can
then use ethereal to examine the traffic and timing for that particular
request.
I will report back my findings, but that will take a couple of days.
regards Henk Fictorie
Rainer Jung-3 wrote:
>
> Can you reprodu
'JkOptions +FlushPackets' to the apache config help?
- can I somehow disable sending the Keep-Alive header to tomcat and will
that help?
Any ideas/remarks?
regards Henk Fictorie
--
Configuration info:
Apache 2.0.59
JkLogLevel info
JkWorkersFile /us
state
Could in the upcoming mod_jk 1.2.20 release this be changed to using the
name of the worker also in the Request Logging.
regards Henk Fictorie
--
View this message in context:
http://www.nabble.com/mod_jk---logging-the-name-of-the-worker-tf2621047.html#a7313837
Sent from the Tomcat - Us
Hi,
In mod_jk 1.2.19 the reference attribute is introduced for a worker. My
question is does inherentance work for this attribute. Example:
worker.template.activation=D
worker.worker1.reference=worker.template
worker.worker1.port=18009
worker.worker2.reference=worker.worker1
Will this result
The Changelog mentions:
Added %R JkRequestLogFormat option for Apache 1 and Apache 2. (mturk)
In the Apache documentation however this new option is not documented. Could
somebody explain (and document) what it does?
regards Henk Fictorie
--
View this message in context:
http
19 matches
Mail list logo