Re: mod_jk 1.2.27 and an empty POST

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 after sending request but before providing POST data

mod_jk 1.2.27 and an empty POST

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 archive at Nabble.com

RE: With JK 1.2.x using route causes problems with redirect?

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=1

Re: mod_jk - connectionTimeout en connection_pool_timeout

. Will 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 'no retries'. I have now

mod_jk - connectionTimeout en connection_pool_timeout

(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://www.nabble.com/mod_jk---connectionTimeout-en

Re: mod_jk - connectionTimeout en connection_pool_timeout

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 new Tomcat version. We now have a split application which is using both Tomcat 5.0

mod_jk 1.2.21 - minor error in status page

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: http

mod_jk - connection_pool_size and connection_pool_minsize

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_pool_minsize

Re: mod_jk - connection_pool_size and connection_pool_minsize

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_minsize is only used when the connection_pool_size

Re: JK 1.2.20 - Sticky session doesn't work properly

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 running on

RE: JK 1.2.20 - Sticky session doesn't work properly

is properly stetted by tomcat, but the loadbalancer choose the wrong worker. Matteo -Original Message- From: Henk Fictorie [mailto:[EMAIL PROTECTED] Sent: mercoledì 10 gennaio 2007 16.10 To: users@tomcat.apache.org Subject: Re: JK 1.2.20 - Sticky session doesn't work properly

Re: Tomcat is sometimes very slow using mod_jk

. 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. Regards, Rainer -- View this message

Re: Tomcat is sometimes very slow using mod_jk

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'll try to find the reason. Would it be easy for you to repeat

Re: Tomcat is sometimes very slow using mod_jk

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? regards Henk Fictorie Rainer Jung-3 wrote: Henk Fictorie

Re: Tomcat is sometimes very slow using mod_jk

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 reproduce

Tomcat is sometimes very slow using mod_jk

+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 /usr/local/apache2/conf

mod_jk - logging the name of the worker

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 - User mailing list

mod_jk 1.2.19 worker reference inherentance question

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

mod_jk.1.2.19 - missing documentation for %R JkRequestLogFormat

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