[jbossweb-commits] JBossWeb SVN: r917 - in branches/2.1.x: webapps/docs and 1 other directory.
Author: remy.maucherat(a)jboss.com
Date: 2009-02-02 07:16:26 -0500 (Mon, 02 Feb 2009)
New Revision: 917
Modified:
branches/2.1.x/java/org/apache/jasper/compiler/Validator.java
branches/2.1.x/webapps/docs/aio.xml
branches/2.1.x/webapps/docs/changelog.xml
Log:
- Port new Validator case sensitivity fix.
- Expand a bit the doc for scalability and syncing.
Modified: branches/2.1.x/java/org/apache/jasper/compiler/Validator.java
===================================================================
--- branches/2.1.x/java/org/apache/jasper/compiler/Validator.java 2009-01-29 21:35:41 UTC
(rev 916)
+++ branches/2.1.x/java/org/apache/jasper/compiler/Validator.java 2009-02-02 12:16:26 UTC
(rev 917)
@@ -37,7 +37,6 @@
import javax.servlet.jsp.tagext.ValidationMessage;
import org.apache.el.lang.ELSupport;
-import org.apache.jasper.Constants;
import org.apache.jasper.JasperException;
import org.apache.jasper.el.ELContextImpl;
import org.xml.sax.Attributes;
Modified: branches/2.1.x/webapps/docs/aio.xml
===================================================================
--- branches/2.1.x/webapps/docs/aio.xml 2009-01-29 21:35:41 UTC (rev 916)
+++ branches/2.1.x/webapps/docs/aio.xml 2009-02-02 12:16:26 UTC (rev 917)
@@ -39,6 +39,15 @@
other source).
</p>
+ <p>
+ The number of concurrent connections that can be handled by JBoss Web is constrained
by the
+ poller size that has been configured on the connector (see the pollerSize attribute
in the APR
+ documentation). JBoss Web uses two separate pollers for keep alive and event
processing, so by
+ default it can handle a maximum of 8192 kept alive connections and 8192 event driven
connections
+ (for event connections, failure to put a socket in the poller will result in the end
of the
+ processing of the connection).
+ </p>
+
<subsection name="HttpEvent">
<p>
@@ -180,6 +189,14 @@
concurrent writes done on the same connection should likely synchronize on the event
object.
</p>
+ <p>
+ When the processing of the END or ERROR event is done, the connection may be closed,
and no
+ additional data should be written on the connection. Unsynchronized asynchronous
writes may
+ cause stability issues when this happens. It is valid however to add the proper
synchronization
+ in the END or ERROR event processing (so that they wait for the asynchronous write
loop to get
+ done rather than synchronizing all writes).
+ </p>
+
</subsection>
<subsection name="HttpEventFilter">
Modified: branches/2.1.x/webapps/docs/changelog.xml
===================================================================
--- branches/2.1.x/webapps/docs/changelog.xml 2009-01-29 21:35:41 UTC (rev 916)
+++ branches/2.1.x/webapps/docs/changelog.xml 2009-02-02 12:16:26 UTC (rev 917)
@@ -16,6 +16,31 @@
<body>
+<section name="JBoss Web 2.1.2.GA (remm)">
+ <subsection name="General">
+ <changelog>
+ </changelog>
+ </subsection>
+ <subsection name="Catalina">
+ <changelog>
+ </changelog>
+ </subsection>
+ <subsection name="Coyote">
+ <changelog>
+ </changelog>
+ </subsection>
+ <subsection name="Jasper">
+ <changelog>
+ <fix>
+ <bug>46564</bug>: More case insensitive comparison of encodings.
(markt)
+ </fix>
+ <fix>
+ Validator code cleanup. (markt)
+ </fix>
+ </changelog>
+ </subsection>
+</section>
+
<section name="JBoss Web 2.1.2.CR1 (remm)">
<subsection name="General">
<changelog>