On Tue, Sep 24, 2013 at 8:15 AM, Igor Urisman wrote:
> Thanks again, Mark, for the quick turnaround.
> Which of the 5 parameters on this page would be responsible for changing
> the 125-byte max whole text message size?
>
Mark did a great job describing the properties and if it's still unclear
lo
mohan.radhakrish...@polarisft.com wrote:
Yes. That is probably the capacity planning part that involves think time
analysis and concurrency.
What Were They Thinking:
Modeling Think Times for Performance Testing
Tom Wilson
from Computer Measurement Group is what I plan to refer to. But don't kn
Thanks again, Mark, for the quick turnaround.
Which of the 5 parameters on this page would be responsible for changing
the 125-byte max whole text message size?
-Igor.
On Mon, Sep 23, 2013 at 9:07 AM, Mark Thomas wrote:
> On 23/09/2013 08:44, Igor Urisman wrote:
> > Thanks for the speedy reply,
Yes. That is probably the capacity planning part that involves think time
analysis and concurrency.
What Were They Thinking:
Modeling Think Times for Performance Testing
Tom Wilson
from Computer Measurement Group is what I plan to refer to. But don't know
yet how to mine this from awstats.
The R
It does have an effect according to the netstat output.
I want to forget this configuration in a production bank server done by
someone :-) It looks like the parser picked up node1, They have ignored
the parser errors wherever it is logged.
node2 loadbalancer is not a node at all. A space is ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kalyan,
On 9/19/13 12:46 PM, Kalyan Vavilapalli wrote:
> I did follow all the links and did not find any answers.
The answer that was awarded 250 reputation points is fairly in-depth.
> Is there a specific link you are referring to that I am
> ove
On Thu, Sep 19, 2013 at 9:03 AM, Daniel Mikusa wrote:
> Here's what I've been using:
>
>
> WEB-INF/web.xml:
>
>
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Casper,
On 9/19/13 2:03 AM, Casper Wandahl Schmidt wrote:
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Subject: Re: Problem building
> Tomcat connector
>
>> Although it does not explicitly state it
Thanks for the speedy reply, Mark.
I have thought about that code for a minute. You're right; what it does is
construct the entire
message in memory. My use case has no use for partials and the message
sizes are
tens to hundreds of Kb. Didn't mean to defeat anything there, just the use
case.
If
On 23/09/2013 08:44, Igor Urisman wrote:
> Thanks for the speedy reply, Mark.
>
> I have thought about that code for a minute. You're right; what it does is
> construct the entire
> message in memory. My use case has no use for partials and the message
> sizes are
> tens to hundreds of Kb. Didn'
Ok, thanks for the advice. If it means removing one more layer of
complexity, I'm all for it.
Best,
Alec
On Fri, Sep 20, 2013 at 11:57 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Alec,
>
> On 9/20/13 2:03 PM, Tomcat Rand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 9/23/13 3:00 AM, André Warnier wrote:
> Do not top-post. It makes it difficult to follow the conversation,
> who answers to what etc.
>
>>
>>
>> From: Daniel Mikusa To: "Tomcat
>> Users List" Date: 09/20/2013 07:10
>> PM Subje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 9/21/13 9:53 AM, chris derham wrote:
>>
>> To add to what Daniel is saying, here is a little graphic
>> representation, for one single client browser :
>>
>> (browser) <-- HTTP --> (httpd + mod_jk) <-- AJP --> (tomcat) <-->
>> (webapp) (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 9/23/13 3:03 AM, André Warnier wrote:
> mohan.radhakrish...@polarisft.com wrote:
>> Hi, I came across this worker.properties that has two workers to
>> balance the load.
>>
>> worker.list=node1,node2 loadbalancer,status
>>
>> This parti
On 22/09/2013 21:49, Igor Urisman wrote:
> However, the server implementation is free to pick the maximum size of a
> payload
> that it is willing to receive as a whole. Tomcat designers chose that size
> to be 125
> bytes. Reasonable number given the particulars of the wire level protocol,
> bu
Who, moi ?
MiB wrote:
23 sep 2013 09.00 André Warnier:
Do not top-post. It makes it difficult to follow the conversation, who answers
to what etc.
From: Daniel Mikusa
To: "Tomcat Users List"
Date: 09/20/2013 07:10 PM
Subject:Re: MaxClients and maxThreads
On Sep 20, 2013, a
23 sep 2013 09.00 André Warnier:
> Do not top-post. It makes it difficult to follow the conversation, who
> answers to what etc.
>
>> From: Daniel Mikusa
>> To: "Tomcat Users List"
>> Date: 09/20/2013 07:10 PM
>> Subject:Re: MaxClients and maxThreads
>> On Sep 20, 2013, at 9:2
mohan.radhakrish...@polarisft.com wrote:
Hi,
I came across this worker.properties that has two workers to
balance the load.
worker.list=node1,node2 loadbalancer,status
This particular line seems to be misconfigured. 'worker.list' has
node1,node2 loadbalancer,status
I think the
Do not top-post. It makes it difficult to follow the conversation, who answers
to what etc.
From: Daniel Mikusa
To: "Tomcat Users List"
Date: 09/20/2013 07:10 PM
Subject:Re: MaxClients and maxThreads
On Sep 20, 2013, at 9:27 AM, mohan.radhakrish...@polarisft.com wrote:
19 matches
Mail list logo
