svn commit: r1088925 - in /tomcat/trunk/webapps/docs/config: ajp.xml http.xml

2011-04-05 Thread timw
Author: timw
Date: Tue Apr  5 08:48:30 2011
New Revision: 1088925

URL: http://svn.apache.org/viewvc?rev=1088925&view=rev
Log:
Clarifying that pollTime parameter is in microseconds, and correcting the ms 
equivalent for HTTP connector use of it.

Modified:
tomcat/trunk/webapps/docs/config/ajp.xml
tomcat/trunk/webapps/docs/config/http.xml

Modified: tomcat/trunk/webapps/docs/config/ajp.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/ajp.xml?rev=1088925&r1=1088924&r2=1088925&view=diff
==
--- tomcat/trunk/webapps/docs/config/ajp.xml (original)
+++ tomcat/trunk/webapps/docs/config/ajp.xml Tue Apr  5 08:48:30 2011
@@ -457,9 +457,10 @@
   
 
   
-Duration of a poll call. Lowering this value will slightly decrease
-latency of connections being kept alive in some cases, but will use 
more
-CPU as more poll calls are being made. The default value is 2000 (2ms).
+Duration of a poll call in microseconds. Lowering this value will
+slightly decrease latency of connections being kept alive in some cases
+, but will use more CPU as more poll calls are being made. The default
+value is 2000 (2ms).
 
 
 

Modified: tomcat/trunk/webapps/docs/config/http.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/http.xml?rev=1088925&r1=1088924&r2=1088925&view=diff
==
--- tomcat/trunk/webapps/docs/config/http.xml (original)
+++ tomcat/trunk/webapps/docs/config/http.xml Tue Apr  5 08:48:30 2011
@@ -736,9 +736,9 @@
   
 
   
-Duration of a poll call. Lowering this value will slightly decrease
-latency of connections being kept alive in some cases, but will use 
more
-CPU as more poll calls are being made. The default value is 2000 (5ms).
+Duration of a poll call in microseconds. Lowering this value will 
slightly
+decrease latency of connections being kept alive in some cases, but 
will use
+more CPU as more poll calls are being made. The default value is 2000 
(2ms).
 
   
 



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



bindOnInit and maxConnections for AJP connectors

2011-04-05 Thread Tim Whittington
In the AJP standard implementation docs, the following are not
mentioned, although they're properties of AbstractEndpoint and
probably should work:
- bindOnInit
- maxConnections
Am I right in assuming these should be possible in the AJP connector
(my reading of the code indicates they are - just wanted to check if
something arcane was going on)?

If so I'll update the docs.

cheers
tim

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: bindOnInit and maxConnections for AJP connectors

2011-04-05 Thread Tim Whittington
Further to this, the docs for maxConnections currently state:

"This setting is currently only applicable to the blocking Java
connectors (AJP/HTTP)."

But both the NIO and APR connectors use this setting in their Acceptor
implementations, limiting the number of concurrent connections before
they're accepted and handed off to the pollers.

It's possibly the case for the APR connector that pollerSize should be
used in preference (keeping maxConnections > pollerSize), but the NIO
connector doesn't have a poller size config option (the connector
summary describes it as 'restricted by mem'.

The Connector Comparison table (and the discussion of
connection/thread behaviour) in the HTTP connector docs are thus
slightly misleading.

Is what's actually going on more like:

APR: use maxConnections == pollerSize (smallest will limit, but if
pollerSize < maxConnections then the socket backlog effectively won't
be used as the poller will keep killing connections as they come in)

NIO: use maxConnections to limit 'poller size'

HTTP: use maxConnections. For keep alive situations, reduce
maxConnections to something closer to maxThreads (the default config
is 10,000 keepalive connections serviced by 200 threads with a 60
second keepalive timeout, which could lead to some large backlogs of
connected sockets that take 50 minutes to get serviced)

cheers
tim

On Tue, Apr 5, 2011 at 8:51 PM, Tim Whittington  wrote:
> In the AJP standard implementation docs, the following are not
> mentioned, although they're properties of AbstractEndpoint and
> probably should work:
> - bindOnInit
> - maxConnections
> Am I right in assuming these should be possible in the AJP connector
> (my reading of the code indicates they are - just wanted to check if
> something arcane was going on)?
>
> If so I'll update the docs.
>
> cheers
> tim
>

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[RESULT] [VOTE] Release Apache Tomcat 7.0.12

2011-04-05 Thread Mark Thomas
The result of the vote is stable with 4 +1 votes (3 from PMC members)
and no other votes.

I'll start moving the files now and announce once the mirrors have
picked them up.

Mark



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Tomcat hardware requirments

2011-04-05 Thread bfackrell

Is this a good place to ask:

What are the hardware requirements for Tomcat 7?  I looked (Google and on
the Apache website)

I’m just finishing a college course that taught Java technologies that
interact with Tomcat but I want to know more so I’ve decided to try to build
my own Tomcat server from scrap computer parts that I have.  The first thing
I need to know is: Will my junk even run Tomcat 7?

-- 
View this message in context: 
http://old.nabble.com/Tomcat-hardware-requirments-tp31326014p31326014.html
Sent from the Tomcat - Dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: Tomcat hardware requirments

2011-04-05 Thread Mark Thomas
On 05/04/2011 17:39, bfackrell wrote:
> 
> Is this a good place to ask:
> 
> What are the hardware requirements for Tomcat 7?  I looked (Google and on
> the Apache website)

No. You want the users mailing list, not the developers mailing list.

Mark

> I’m just finishing a college course that taught Java technologies that
> interact with Tomcat but I want to know more so I’ve decided to try to build
> my own Tomcat server from scrap computer parts that I have.  The first thing
> I need to know is: Will my junk even run Tomcat 7?
> 




-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: bindOnInit and maxConnections for AJP connectors

2011-04-05 Thread Sylvain Laurent

On 5 avr. 2011, at 11:50, Tim Whittington wrote:
> 
> HTTP: use maxConnections. For keep alive situations, reduce
> maxConnections to something closer to maxThreads (the default config
> is 10,000 keepalive connections serviced by 200 threads with a 60
> second keepalive timeout, which could lead to some large backlogs of
> connected sockets that take 50 minutes to get serviced)

I think it was tc6 behavior, but it changed with tc7 : threads are now returned 
to the pool between requests, even with keep-alive connections.

Sylvain
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: bindOnInit and maxConnections for AJP connectors

2011-04-05 Thread Mark Thomas
On 05/04/2011 19:42, Sylvain Laurent wrote:
> 
> On 5 avr. 2011, at 11:50, Tim Whittington wrote:
>>
>> HTTP: use maxConnections. For keep alive situations, reduce
>> maxConnections to something closer to maxThreads (the default config
>> is 10,000 keepalive connections serviced by 200 threads with a 60
>> second keepalive timeout, which could lead to some large backlogs of
>> connected sockets that take 50 minutes to get serviced)
> 
> I think it was tc6 behavior

Nope. tc6 behaviour was one thread per connection, including during
keep-alive.

, but it changed with tc7 : threads are now returned to the pool between
requests, even with keep-alive connections.

tc7 behaviour does return the thread to the pool but it is certainly
possible for something along the lines Tim is describing to happen
although I don't think the delay could be as long as 50 minutes. I'd
need to double check the code for keep-alive time-outs to be sure.

Mark



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r1089202 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-04-05 Thread markt
Author: markt
Date: Tue Apr  5 20:17:41 2011
New Revision: 1089202

URL: http://svn.apache.org/viewvc?rev=1089202&view=rev
Log:
Vote

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=1089202&r1=1089201&r2=1089202&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Apr  5 20:17:41 2011
@@ -175,13 +175,13 @@ PATCHES PROPOSED TO BACKPORT:
 * Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=49180
   Add option to disable log rotation in juli FileHandler
   https://issues.apache.org/bugzilla/attachment.cgi?id=26844
-  +1: kkolinko
+  +1: kkolinko, markt
   -1:
 
 * Clarify error messages in *.sh files to mention that if a script is not
   found it might be because execute permission is needed.
   http://svn.apache.org/viewvc?rev=1088179&view=rev
-  +1: kkolinko
+  +1: kkolinko, markt
   -1:
 
 * Update download paths in build.properties.default:
@@ -189,10 +189,10 @@ PATCHES PROPOSED TO BACKPORT:
   one. These downloads are needed when building extras.
   It is backport of r1072962
   http://people.apache.org/~kkolinko/patches/2011-04-03_tc6_maven2.patch
-  +1: kkolinko
+  +1: kkolinko, markt
   -1:
 
 * Implement display of multiple request headers in AccessLogValve
   http://svn.apache.org/viewvc?rev=1088460&view=rev
-  +1: kkolinko
+  +1: kkolinko, markt
   -1:



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org