[
https://jira.jboss.org/jira/browse/JBWEB-142?page=com.atlassian.jira.plug...
]
Mike Millson commented on JBWEB-142:
------------------------------------
Test Case:
1) Take heap with default configuration. Inspect org.apache.jasper.Constants and verify
that DEFAULT_TAG_BUFFER_SIZE is 512. See attached default.png.
2) Add the following JVM option to run.conf:
-Dorg.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE=1001
3) Take heap with default configuration. Inspect org.apache.jasper.Constants and verify
that DEFAULT_TAG_BUFFER_SIZE is 1001. See attached set-to-1001.png.
Modifiable org.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE
--------------------------------------------------------------
Key: JBWEB-142
URL:
https://jira.jboss.org/jira/browse/JBWEB-142
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Tomcat
Affects Versions: JBossWeb-2.0.0.GA_CP10
Reporter: Mike Millson
Assignee: Remy Maucherat
Attachments: jbweb-142.patch
Add functionality to parameterize the buffer size of
org.apache.jasper.runtime.BodyContentImpl.java (e.g. with an environment variable).
Currently the buffer size is determined by the
org.apache.jasper.Constants.DEFAULT_TAG_BUFFER_SIZE constant, which is set 512 bytes, and
there is no way to override this.
Applications with many JSP pages that are larger than 512 bytes would benefit from a
larger buffer size by avoiding excessive GC due to creating and destroying char arrays.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira