321greetings auto responder
Hi, Due to the amount of e-mails we get per day we have setup this auto responder for your convenience. This is not a monitored e-mail address To unsubscribe http://321greetings.com/unsubscribenewlist.htm a href=\ http://321greetings.com/unsubscribenewlist.htm \ AOL Link /a To subscribe please go here: http://321greetings.com/sub321greetings-newsletter.htm a href=\ http://321greetings.com/sub321greetings-newsletter.htm \ AOL Link /a If you need technical assistance, please go here: http://321greetings.com/contactus.htm a href=\ http://321greetings.com/contactus.htm \ AOL-link /a - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser XMLEncodingDetector.java
Remy Maucherat wrote: Is it a standalone class or something like this ? If it is - copy paste into the Jasper code and remove the funky loading logic. (I thought JDK 1.5 was supposed to include the same Xerces 2 we were using - what happened ?) Follow up: the Xerces packages got renamed to com.sun.org.apache.xerces.internal.*. So we have two options, one which I like and one which I don't like: a) Write a XercesJava5EncodingDetector class with the right classnames b) As the 5 classes used by the XercesEncodingDetector are self contained, we could copy them to the o.a.jasper.xmlparser package, so that Jasper can be spec compliant even without Xerces installed, merge the content of XercesEncodingDetector into XMLEncodingDetector, and remove the dynamic loading of Xerces Since I think it's not acceptable to require Xerces to be compliant, I would choose b). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina build.xml
remm2004/10/01 02:00:16
Modified:catalina build.xml
Log:
- Move naming-resources to server (it seems to work).
- Merge all the ENC related stuff in a single JAR (I don't think it was useful
keeping all the micro JARs around).
- Comment out copying jk2.properties for now.
Revision ChangesPath
1.75 +4 -34 jakarta-tomcat-catalina/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- build.xml 24 Sep 2004 16:41:12 - 1.74
+++ build.xml 1 Oct 2004 09:00:16 - 1.75
@@ -697,8 +697,10 @@
copy tofile=${catalina.deploy}/server/lib/tomcat-ajp.jar
file=${tomcat-jk2.jar}/
--
+ !--
copy todir=${catalina.deploy}/conf
file=${jk2.properties}/
+--
/target
@@ -1017,43 +1019,11 @@
/fileset
/jar
-!-- Naming - Common JAR File --
-jar jarfile=${catalina.deploy}/common/lib/naming-common.jar
- index=true
- fileset dir=${classes.dir}
-include name=org/apache/naming/* /
-include name=org/apache/naming/factory/Constants.class /
-include name=org/apache/naming/factory/ResourceLinkFactory.class /
-exclude name=org/apache/naming/java/* /
-!--
-exclude name=org/apache/naming/JndiPermission.class /
---
-
-!-- Javadoc and i18n exclusions --
-exclude name=**/package.html /
-exclude name=**/LocalStrings_* /
-
- /fileset
-/jar
-
-!-- Naming - Java: namespace. It shouldn't be included if tomcat is used
inside a different
- container that provides this ns --
-jar jarfile=${catalina.deploy}/common/lib/naming-java.jar index=true
- fileset dir=${classes.dir}
-include name=org/apache/naming/java/* /
-!-- Javadoc and i18n exclusions --
-exclude name=**/package.html /
-exclude name=**/LocalStrings_* /
- /fileset
-/jar
-
-
!-- Naming - Factory JAR File --
jar jarfile=${catalina.deploy}/common/lib/naming-factory.jar index=true
fileset dir=${classes.dir}
+include name=org/apache/naming/* /
include name=org/apache/naming/factory/** /
-exclude name=org/apache/naming/factory/Constants.class /
-exclude name=org/apache/naming/factory/ResourceLinkFactory.class /
!-- Javadoc and i18n exclusions --
exclude name=**/package.html /
exclude name=**/LocalStrings_* /
@@ -1061,7 +1031,7 @@
/jar
!-- Naming - Resources JAR File --
-jar jarfile=${catalina.deploy}/common/lib/naming-resources.jar index=true
+jar jarfile=${catalina.deploy}/server/lib/naming-resources.jar index=true
fileset dir=${classes.dir}
include name=org/apache/naming/JndiPermission.class /
include name=org/apache/naming/NameParserImpl.class /
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina build.xml
remm2004/10/01 02:12:56
Modified:catalina build.xml
Log:
- Oops: fix packaging mistake.
Revision ChangesPath
1.76 +3 -3 jakarta-tomcat-catalina/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -r1.75 -r1.76
--- build.xml 1 Oct 2004 09:00:16 - 1.75
+++ build.xml 1 Oct 2004 09:12:56 - 1.76
@@ -1022,8 +1022,8 @@
!-- Naming - Factory JAR File --
jar jarfile=${catalina.deploy}/common/lib/naming-factory.jar index=true
fileset dir=${classes.dir}
-include name=org/apache/naming/* /
-include name=org/apache/naming/factory/** /
+include name=org/apache/naming/** /
+exclude name=org/apache/naming/resources/** /
!-- Javadoc and i18n exclusions --
exclude name=**/package.html /
exclude name=**/LocalStrings_* /
@@ -1039,7 +1039,7 @@
include name=org/apache/naming/NamingContextEnumeration.class /
include name=org/apache/naming/NamingEntry.class /
include name=org/apache/naming/StringManager.class /
-include name=org/apache/naming/resources/* /
+include name=org/apache/naming/resources/** /
!-- Javadoc and i18n exclusions --
exclude name=**/package.html /
exclude name=**/LocalStrings_* /
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26372] - java.lang.ThreadDeath when trwaing to reload an application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=26372. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 java.lang.ThreadDeath when trwaing to reload an application --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 09:22 --- Can confirm that the ThreadDeath is still occurring after every class compile that causes a webapp reload by Tomcat resulting in total failure of Tomcat with the following in our contextDestroyed LogManager.shutdown(); java.beans.Introspector.flushCaches(); LogFactory.releaseAll(); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader WebappClassLoader.java
remm2004/10/01 02:30:00
Modified:catalina/src/share/org/apache/catalina/loader
WebappClassLoader.java
Log:
- I think the package triggers are no longer useful (especially on JDK 1.5, where
everything got package renamed).
- On JDK 1.4, there won't be any problem if Xerces and Xalan are endorsed (AFAIK,
they need to be to be able to be used).
Revision ChangesPath
1.43 +1 -6
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader/WebappClassLoader.java
Index: WebappClassLoader.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader/WebappClassLoader.java,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- WebappClassLoader.java29 Aug 2004 16:46:10 - 1.42
+++ WebappClassLoader.java1 Oct 2004 09:30:00 - 1.43
@@ -146,11 +146,6 @@
* class loader without delegating first.
*/
private static final String[] packageTriggers = {
-javax, // Java extensions
-org.xml.sax, // SAX 1 2
-org.w3c.dom, // DOM 1 2
-org.apache.xerces, // Xerces 1 2
-org.apache.xalan // Xalan
};
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26372] - java.lang.ThreadDeath when trwaing to reload an application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=26372. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 java.lang.ThreadDeath when trwaing to reload an application --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 10:23 --- Allistair, Do you observe any difference when you configure log4j only by using BasisConfigurator.configure()? I mean without calling PropertyConfigurator or DOMConfigruator... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm JAASRealm.java
yoavs 2004/10/01 05:28:00
Modified:catalina/src/share/org/apache/catalina/realm JAASRealm.java
Log:
Fixed my mistake when applying patch for Bugzilla 28631.
Revision ChangesPath
1.10 +1 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JAASRealm.java
Index: JAASRealm.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JAASRealm.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- JAASRealm.java21 Sep 2004 23:29:33 - 1.9
+++ JAASRealm.java1 Oct 2004 12:28:00 - 1.10
@@ -540,10 +540,6 @@
}
if (roleClasses.contains(principalClass)) {
-roles.add(principal.getName());
-}
-
-if (roleClasses.contains(principalClass)) {
roles.add(principal);
if( log.isDebugEnabled() ) {
log.debug(sm.getString(jaasRealm.rolePrincipalAdd,
principal.getName()));
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm JAASRealm.java
yoavs 2004/10/01 05:28:47
Modified:catalina/src/share/org/apache/catalina/realm Tag: TOMCAT_5_0
JAASRealm.java
Log:
Fixed my mixtake when applying patch for Bugzilla 28631.
Revision ChangesPath
No revision
No revision
1.6.2.4 +1 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JAASRealm.java
Index: JAASRealm.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JAASRealm.java,v
retrieving revision 1.6.2.3
retrieving revision 1.6.2.4
diff -u -r1.6.2.3 -r1.6.2.4
--- JAASRealm.java21 Sep 2004 23:01:50 - 1.6.2.3
+++ JAASRealm.java1 Oct 2004 12:28:47 - 1.6.2.4
@@ -541,10 +541,6 @@
}
if (roleClasses.contains(principalClass)) {
-roles.add(principal.getName());
-}
-
-if (roleClasses.contains(principalClass)) {
roles.add(principal);
if( log.isDebugEnabled() ) {
log.debug(sm.getString(jaasRealm.rolePrincipalAdd,
principal.getName()));
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 12:31 --- My mistake -- good catch. Thank you for pointing it out. I've fixed it on both HEAD and TOMCAT_5_0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31309] - Deploy fails when deploying from path with international characters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31309. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31309 Deploy fails when deploying from path with international characters --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 12:48 --- Hmm. Is your JVM's default charset set appropriately? Check by testing that Locale.getDefault() returns a Locale that can handle your encoding (German in your case). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31504] New: - Method GET decodes wrong, POST decodes ok
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31504. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31504 Method GET decodes wrong, POST decodes ok Summary: Method GET decodes wrong, POST decodes ok Product: Tomcat 5 Version: 5.0.28 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If I use html form with method GET, Tomcat doesn't decode URL parameters in correct way. You can submit the JSP file bellow with parameter example.jsp?input=%C5%BEena The correct result should look like 'zena' (with accented letter 'z'), but the value shown is 'žena'. If you run the example with Tomcat 4.1, you would see the correct result. I'm not sure which component causes this behaviour so I choose Catalina. Tomcat versions: 4.1.x - ok 5.0.28 - KO 5.5.2 - KO example JSP file: %@ page contentType=text/html;charset=utf-8 language=java %% request.setCharacterEncoding(utf-8); String value = request.getParameter(input); if (value == null) value = ; % html head meta http-equiv=Content-Type content=text/html; charset=utf-8 /head body form action=# method=get input type=text name=input value=%=value% input type=submit value=Submit /form /body /html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31504] - Method GET decodes wrong, POST decodes ok
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31504. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31504 Method GET decodes wrong, POST decodes ok [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 12:58 --- This has been beaten to death and verified numerous times including by the JSP Spec leads. You do need to ensure your configuration is OK, e.g. setting the URI encoding parameter on the Connector element in server.xml, your JVM locale, your LANG environment variables, etc. Search the mailing list archives if you wish for some complete examples, and please post there rather than reopening this issue if you still can't get your environment configured properly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: hi
Please read the document. Norton AntiVirus eliminato1.txt Description: plain/text - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tina Dexter/HCUK is out of the office.
I will be out of the office starting 01/10/2004 and will not return until 07/10/2004. I will be on holiday from Friday 1st October returning on Thursday 7th October If you have any urgent queries during this time, please contact my colleagues Liz Vasey (01494 428 622) or Jennie Egan (01494 428691. ** This document should only be read by those persons to whom it is addressed and is not intended to be relied upon by any person without subsequent written confirmation of its contents. Accordingly, Hyundai Car (UK) disclaim all responsibility and accept no liability (including in negligence) for the consequences for any person acting, or refraining from acting, on such information prior to the receipt by those persons of subsequent written confirmation. If you have received this E-mail message in error, please notify us immediately by telephone on +44 (0) 1494 428 690. Please also destroy and delete the message from your computer. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this E-mail message is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Automated reply from bulletproof@www.bulletproofsoft.com
BulletProofSoft.com Support Ticket Reply. DO NOT REPLY TO THIS EMAIL Please use our Online Support system for faster results to your questions. You can monitor the status of your ticket online where you can add follow up replies. http://www.bulletproofsoft.com/cgi-bin/custquest/quest_desk.cgi If the URL above splits into two lines, please visit: http://www.bulletproofsoft.com/support.html and click on the Contact Customer Support link Rest assured we will do our best to respond to your query promptly. You will receive a further email notification when one of our technicians has replied. Tech Support BulletProofSoft.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser XMLEncodingDetector.java
Remy Maucherat wrote: Remy Maucherat wrote: Is it a standalone class or something like this ? If it is - copy paste into the Jasper code and remove the funky loading logic. (I thought JDK 1.5 was supposed to include the same Xerces 2 we were using - what happened ?) Follow up: the Xerces packages got renamed to com.sun.org.apache.xerces.internal.*. So we have two options, one which I like and one which I don't like: a) Write a XercesJava5EncodingDetector class with the right classnames b) As the 5 classes used by the XercesEncodingDetector are self contained, we could copy them to the o.a.jasper.xmlparser package, so that Jasper can be spec compliant even without Xerces installed, merge the content of XercesEncodingDetector into XMLEncodingDetector, and remove the dynamic loading of Xerces Since I think it's not acceptable to require Xerces to be compliant, I would choose b). Agreed. Will make these changes. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: jakarta-tomcat-5/jakarta-tomcat-dbcp failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project jakarta-tomcat-dbcp has an issue affecting its community integration. This issue affects 14 projects, and has been outstanding for 99L runs. Project State : 'Failed' The following are affected: - avalon-http-context : Avalon SVN - avalon-http-demo : Avalon SVN - avalon-http-examples : Avalon SVN - avalon-http-impl : Avalon SVN - avalon-http-server : Avalon SVN - avalon-http-servlet : Avalon SVN - avalon-http-static : Avalon SVN - avalon-http-test : Avalon SVN - avalon-planet-facilities : Avalon SVN - jakarta-tomcat-5 : Servlet 2.4 and JSP 2.0 Reference Implementation - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-dbcp : Servlet 2.4 and JSP 2.0 Reference Implementation - jakarta-tomcat-jk : Connectors to various web servers - metro-reflector-blocks-complete : Avalon SVN Full details are available at: http://brutus.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Sole output [naming-factory-dbcp.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-dbcp.html Work Name: build_jakarta-tomcat-5_jakarta-tomcat-dbcp (Type: Build) State: Failed Elapsed: 4 secs Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcommons-collections.home=/usr/local/gump/public/workspace/jakarta-commons/collections -Dcommons-dbcp.home=/usr/local/gump/public/workspace/jakarta-commons/dbcp -Dcommons-dbcp.version=01102004 -Dtomcat-dbcp.home=/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps -Dcommons-pool.home=/usr/local/gump/public/workspace/jakarta-commons/pool build-tomcat-dbcp [Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-5] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar- Buildfile: build.xml build-tomcat-dbcp: -build-tomcat-dbcp: [copy] Copying 65 files to /usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps [mkdir] Created dir: /usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp BUILD FAILED /usr/local/gump/public/workspace/jakarta-tomcat-5/build.xml:628: The following error occurred while executing this line: /usr/local/gump/public/workspace/jakarta-tomcat-5/build.xml:663: Cannot replace directory /usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp with directory /usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/commons Total time: 4 seconds - To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/rss.xml Atom: http://brutus.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/atom.xml -- Gump E-mail Identifier (within run) #12. Produced by Gump 2.1.0-alpha-0003. [Run (39390901102004, brutus:brutus-public:39390901102004)] http://brutus.apache.org/gump/public/index.html http://brutus.apache.org/gump/public/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Proposal: 5.0.29 release next Wednesday, October 6th
Hi, I propose to cut the 5.0.29 release next Wednesday, October 6th, at 1500h GMT. There is no rush, but there is a significant number of items in the changelog (34 or so: http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/webapps/docs/c hangelog.xml?only_with_tag=TOMCAT_5_0), and I feel from looking at the code and looking at Bugzilla that this is a good time to cut the release. Does that seem OK for everyone? The usual release procedures will be followed of course. Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE][RESULT] Tomcat 5.5.2 Stability
Hi, This past Monday I posted a vote on 5.5.2 stability: http://marc.theaimsgroup.com/?l=tomcat-devm=109628849208040w=2. The results are as follows: Alpha: Remy, Costin, Mladen (I think, taking liberty to interpret his I agree with Costin statement as a vote ;)) Beta: Jean-Francois, myself So with a narrow majority, we'll keep 5.5.2 as alpha and I will not make any announcement to the user and community lists, which already know it as alpha. In any case I think the vote is mostly moot, since 5.5.3 is coming soon and the points made in Remy's voting email are enough to convince me 5.5.2 should stay alpha anyhow. So with 5.5.2 staying where it is, when shall I cut 5.5.3? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser EncodingMap.java SymbolTable.java XMLChar.java XMLString.java XMLStringBuffer.java XMLEncodingDetector.java XercesEncodingDetector.java
luehe 2004/10/01 12:24:35 Modified:jasper2/src/share/org/apache/jasper/xmlparser XMLEncodingDetector.java Added: jasper2/src/share/org/apache/jasper/xmlparser EncodingMap.java SymbolTable.java XMLChar.java XMLString.java XMLStringBuffer.java Removed: jasper2/src/share/org/apache/jasper/xmlparser XercesEncodingDetector.java Log: Copied XML encoding detection logic into JASPER, so we're no longer dependent on Xerces. All JSP TCKs are passing again. Revision ChangesPath 1.10 +1577 -29 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLEncodingDetector.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLEncodingDetector.java.diff?r1=1.9r2=1.10 1.1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/EncodingMap.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/EncodingMap.java?rev=1.1 1.1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/SymbolTable.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/SymbolTable.java?rev=1.1 1.1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLChar.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLChar.java?rev=1.1 1.1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLString.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLString.java?rev=1.1 1.1 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLStringBuffer.java http://cvs.apache.org/viewcvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/xmlparser/XMLStringBuffer.java?rev=1.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
luehe 2004/10/01 13:01:37 Modified:webapps/docs changelog.xml Log: Copied XML encoding detection logic into JASPER, so we're no longer dependent on Xerces. All JSP TCKs are passing again. Revision ChangesPath 1.124 +3 -0 jakarta-tomcat-catalina/webapps/docs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v retrieving revision 1.123 retrieving revision 1.124 diff -u -r1.123 -r1.124 --- changelog.xml 30 Sep 2004 15:58:32 - 1.123 +++ changelog.xml 1 Oct 2004 20:01:37 - 1.124 @@ -97,6 +97,9 @@ fix bug31257/bug: Added specification of endorsed dirs if forking. Note that this is fairly useless for now in 5.5 since it uses JDT and not javac by default. (yoavs) /fix + fix +Copied XML encoding detection logic into JASPER, so we're no longer dependent on Xerces. (luehe) + /fix /changelog /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Tomcat 4.1.31
From: Keith Wannamaker [mailto:[EMAIL PROTECTED] Ballot [ ] Alpha [ ] Beta [X] Stable /Ballot Looks good to me. Let's get it out there ;) I am still working my way through the TC4 entries in bugzilla so there may well be a need for a 4.1.32 but not for a while. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Tomcat 4.1.31
Hola, Just out of curiosity, don't you need 3 binding +1 votes to get this out there? According to http://jakarta.apache.org/site/decisions.html, this is a Release Testing vote that requires Majority approval, and the same page defines Majority approval as An action requiring majority approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes. I can't vote because I haven't tested this release, but I hope someone else with a binding vote has or will test it, so you can get your three +1s. Yoav Shapira Millennium Research Informatics -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, October 01, 2004 4:07 PM To: 'Tomcat Developers List' Subject: RE: [VOTE] Tomcat 4.1.31 From: Keith Wannamaker [mailto:[EMAIL PROTECTED] Ballot [ ] Alpha [ ] Beta [X] Stable /Ballot Looks good to me. Let's get it out there ;) I am still working my way through the TC4 entries in bugzilla so there may well be a need for a 4.1.32 but not for a while. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Tomcat 4.1.31
From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Hola, Just out of curiosity, don't you need 3 binding +1 votes to get this out there? Indeed we do. Didn't mean to give the impression otherwise. I can't vote because I haven't tested this release, but I hope someone else with a binding vote has or will test it, so you can get your three +1s. Indeed! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalOutputBuffer.java Constants.java Http11Processor.java
remm2004/10/01 16:36:15
Modified:http11/src/java/org/apache/coyote/http11
InternalOutputBuffer.java Constants.java
Http11Processor.java
Log:
- Fix a oops with my usage of constant bytes arrays. So, ok, I can't do that.
- Use a byte array for server.
Revision ChangesPath
1.24 +1 -1
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java
Index: InternalOutputBuffer.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- InternalOutputBuffer.java 31 Aug 2004 23:52:51 - 1.23
+++ InternalOutputBuffer.java 1 Oct 2004 23:36:15 - 1.24
@@ -682,7 +682,7 @@
*
* @param b data to be written
*/
-protected void write(byte[] b) {
+public void write(byte[] b) {
// Writing the byte chunk to the output buffer
System.arraycopy(b, 0, buf, pos, b.length);
1.24 +12 -10
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Constants.java
Index: Constants.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Constants.java,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- Constants.java29 Sep 2004 09:54:28 - 1.23
+++ Constants.java1 Oct 2004 23:36:15 - 1.24
@@ -41,9 +41,15 @@
/**
+ * CRLF.
+ */
+public static final String CRLF = \r\n;
+
+
+/**
* Server string.
*/
-public static final byte[] SERVER_BYTES = convertToBytes(Apache-Coyote/1.1);
+public static final byte[] SERVER_BYTES = convertToBytes(Server:
Apache-Coyote/1.1 + CRLF);
/**
@@ -112,21 +118,17 @@
public static final int DEFAULT_HTTP_HEADER_BUFFER_SIZE = 48 * 1024;
-/**
- * CRLF.
- */
-public static final String CRLF = \r\n;
-
-
/* Various constant strings */
public static final byte[] CRLF_BYTES = convertToBytes(CRLF);
public static final byte[] COLON_BYTES = convertToBytes(: );
-public static final byte[] CONNECTION_BYTES = convertToBytes(Connection);
+public static final String CONNECTION = Connection;
+public static final String CLOSE = close;
public static final byte[] CLOSE_BYTES = convertToBytes(close);
+public static final String KEEPALIVE = keep-alive;
public static final byte[] KEEPALIVE_BYTES = convertToBytes(keep-alive);
-public static final byte[] CHUNKED_BYTES = convertToBytes(chunked);
+public static final String CHUNKED = chunked;
public static final byte[] ACK_BYTES = convertToBytes(HTTP/1.1 100 Continue +
CRLF + CRLF);
-public static final byte[] TRANSFERENCODING_BYTES =
convertToBytes(Transfer-Encoding);
+public static final String TRANSFERENCODING = Transfer-Encoding;
/**
1.112 +10 -15
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
Index: Http11Processor.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- Http11Processor.java 29 Sep 2004 09:54:28 - 1.111
+++ Http11Processor.java 1 Oct 2004 23:36:15 - 1.112
@@ -1500,9 +1500,7 @@
outputBuffer.addActiveFilter
(outputFilters[Constants.CHUNKED_FILTER]);
contentDelimitation = true;
-headers.addValue(Constants.TRANSFERENCODING_BYTES,
-0, Constants.TRANSFERENCODING_BYTES.length).setBytes
-(Constants.CHUNKED_BYTES, 0, Constants.CHUNKED_BYTES.length);
+
headers.addValue(Constants.TRANSFERENCODING).setString(Constants.CHUNKED);
} else {
outputBuffer.addActiveFilter
(outputFilters[Constants.IDENTITY_FILTER]);
@@ -1531,14 +1529,6 @@
}
headers.setValue(Date).setString(date);
-// Add server header
-if (server != null) {
-headers.setValue(Server).setString(server);
-} else {
-headers.setValue(Server).setBytes(Constants.SERVER_BYTES,
-0, Constants.SERVER_BYTES.length);
-}
-
// FIXME: Add transfer encoding header
if ((entityBody) (!contentDelimitation)) {
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalOutputBuffer.java Constants.java Http11Processor.java
I am out of the office until Monday 4 October. If your enquiry is urgent please contact [EMAIL PROTECTED], otherwise I will get back to you on my return. Best Regards, Jim Ansdell See (Nottingham) dl: 0115 9129179 f: 0115 9484345 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Protocol.java
remm2004/10/01 16:46:57
Modified:util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java
http11/src/java/org/apache/coyote/http11 Http11Protocol.java
Added: util/java/org/apache/tomcat/util/net
LeaderFollowerWorkerThread.java
MasterSlaveWorkerThread.java
Log:
- Hack in an alternate thread pool strategy (which is basically the TC 4.0 thread
pool).
- The problem is that there are some environments where the default thread pool
doesn't work well, and there's some black magic
involved with it.
- Another advantage of the thread pool is that its simple design allows server
socket restart to mostly work (at least in TC 4.0 it worked), so
I think this is a good endpoint for not-that-stable VMs/OS combinations. A
drawback is that the thread pool won't scale back (OTOH, scaling
back is dangerous as it could cause memory leaks depending on what the application
is doing).
- I think in the future we could try to use the Java 5 thread pool (although for
now, I haven't figured out a way to use it efficiently with
our stuff).
- Similarly, I haven't found a way to use ThreadPool efficiently with a dedicated
socket listener thread. So the code is in PTcpEndpoint.
- From an efficiency standpoint, there's no measureable difference between the two
thread pools on a 1 CPU machine (no big surprise).
- The default obviously remains the current thread pool.
Revision ChangesPath
1.39 +227 -159
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/PoolTcpEndpoint.java
Index: PoolTcpEndpoint.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/PoolTcpEndpoint.java,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- PoolTcpEndpoint.java 13 Jul 2004 09:43:59 - 1.38
+++ PoolTcpEndpoint.java 1 Oct 2004 23:46:57 - 1.39
@@ -24,6 +24,8 @@
import java.net.Socket;
import java.net.SocketException;
import java.security.AccessControlException;
+import java.util.Stack;
+import java.util.Vector;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
@@ -54,7 +56,9 @@
* @author Gal Shachor [EMAIL PROTECTED]
* @author Yoav Shapira [EMAIL PROTECTED]
*/
-public class PoolTcpEndpoint { // implements Endpoint {
+public class PoolTcpEndpoint implements Runnable { // implements Endpoint {
+
+static Log log=LogFactory.getLog(PoolTcpEndpoint.class );
private StringManager sm =
StringManager.getManager(org.apache.tomcat.util.net.res);
@@ -64,33 +68,46 @@
private final Object threadSync = new Object();
-private boolean isPool = true;
-
private int backlog = BACKLOG;
private int serverTimeout = TIMEOUT;
-TcpConnectionHandler handler;
-
private InetAddress inet;
private int port;
private ServerSocketFactory factory;
private ServerSocket serverSocket;
-ThreadPoolRunnable listener;
private volatile boolean running = false;
private volatile boolean paused = false;
private boolean initialized = false;
private boolean reinitializing = false;
static final int debug=0;
-ThreadPool tp;
-
-static Log log=LogFactory.getLog(PoolTcpEndpoint.class );
-
protected boolean tcpNoDelay=false;
protected int linger=100;
protected int socketTimeout=-1;
+private boolean lf = false;
+
+
+// -- Leader follower fields
+
+
+TcpConnectionHandler handler;
+ThreadPoolRunnable listener;
+ThreadPool tp;
+
+
+// -- Master slave fields
+
+/* The background thread. */
+private Thread thread = null;
+/* Available processors. */
+private Stack workerThreads = new Stack();
+private int curThreads = 0;
+private int maxThreads = 20;
+/* All processors which have been created. */
+private Vector created = new Vector();
+
public PoolTcpEndpoint() {
tp = new ThreadPool();
@@ -102,14 +119,6 @@
// Configuration
-public void setPoolOn(boolean isPool) {
-this.isPool = isPool;
-}
-
-public boolean isPoolOn() {
-return isPool;
-}
-
public void setMaxThreads(int maxThreads) {
if( maxThreads 0)
tp.setMaxThreads(maxThreads);
@@ -247,13 +256,37 @@
serverTimeout=i;
}
+public String getStrategy() {
+if (lf) {
+return lf;
+} else {
+return ms;
+}
+}
+
+public void setStrategy(String strategy) {
+if (ms.equals(strategy)) {
+
cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
remm2004/10/01 16:52:32 Modified:webapps/docs/config http.xml webapps/docs changelog.xml Log: - Changelog update (including my 5.5.2 changes). Revision ChangesPath 1.17 +10 -0 jakarta-tomcat-catalina/webapps/docs/config/http.xml Index: http.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/http.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- http.xml 27 Sep 2004 16:00:31 - 1.16 +++ http.xml 1 Oct 2004 23:52:32 - 1.17 @@ -295,6 +295,16 @@ /p /attribute +attribute name=strategy required=false + pThe thread pooling strategy which will be used. The default strategy does + not use a master thread, but a more conventional strategy using a + master listener thread can be used by setting ms as this attribute's value. + The master strategy will work significantly better using the threadPriority + attribute, which will apply only to the thread which listens on the server socket. + This is set to codelf/code by default. + /p +/attribute + /attributes /subsection 1.125 +84 -3 jakarta-tomcat-catalina/webapps/docs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v retrieving revision 1.124 retrieving revision 1.125 diff -u -r1.124 -r1.125 --- changelog.xml 1 Oct 2004 20:01:37 - 1.124 +++ changelog.xml 1 Oct 2004 23:52:32 - 1.125 @@ -27,10 +27,16 @@ /section section name=Tomcat 5.5.3 (yoavs) + subsection name=General -fix - bug30568/bug: Incomplete setup.html documentation for launching jsvc. (yoavs) -/fix +changelog + fix +bug30568/bug: Incomplete setup.html documentation for launching jsvc. (yoavs) + /fix + update +Repackage naming features. (remm) + /update +/changelog /subsection subsection name=Catalina @@ -78,6 +84,29 @@ fix Fixed StandardContext.getStartTime() to return actual start time/date instead of time (startupTime) it took to start context. (luehe) /fix + update +getRequest/getResponse should return the most relevant interface, to avoid casts. (remm) + /update + update +Add check for directory before considering something is a compressed WAR. (remm) + /update + docs +Update the connector documentation. (remm) + /docs + fix +When parsing a context file, ignore the path attribute: +the only place where it is acceptable is in server.xml. (remm) + /fix + fix +Digester handling fixes: always call reset in a finally block after using a digester. (remm) + /fix + update +Remove many fields from Connector, and tie the creation of the Connector to the +creation of the protocol handler. (remm) + /update + update +Remove package triggers from the classloader, which seem useless when using Java 5. (remm) + /update /changelog /subsection @@ -86,6 +115,22 @@ update Allow customized server header for Standalone. (funkman) /update + fix +Digester.reset now removes the error handler, the root and calls clear, to prevent +any memory leak. (remm) + /fix + update +Remove useless stuff in digester. (remm) + /update + update +In HTTP, add a utility method to convert strings to byte arrays, and output the server header +directly as bytes. (remm) + /update + add +Add a master slave thread pool based on the code from Tomcat 4.0. It is less exotic than the +default one, and might fare better on some picky systems, such as Redhat 9. The two threadpools +will likely be removed once we use the Java 5 API, although more investigation is needed. (remm) + /add /changelog /subsection @@ -97,6 +142,9 @@ fix bug31257/bug: Added specification of endorsed dirs if forking. Note that this is fairly useless for now in 5.5 since it uses JDT and not javac by default. (yoavs) /fix + docs +Document new Jasper defaults, and update the production configuration. (remm) + /docs fix Copied XML encoding detection logic into JASPER, so we're no longer dependent on Xerces. (luehe) /fix @@ -128,6 +176,12 @@ update Added contexts' start time (available from 'startTime' MBean attribute of StandardContext) to status
Re: [VOTE][RESULT] Tomcat 5.5.2 Stability
Shapira, Yoav wrote: Hi, This past Monday I posted a vote on 5.5.2 stability: http://marc.theaimsgroup.com/?l=tomcat-devm=109628849208040w=2. The results are as follows: Alpha: Remy, Costin, Mladen (I think, taking liberty to interpret his I agree with Costin statement as a vote ;)) Beta: Jean-Francois, myself So with a narrow majority, we'll keep 5.5.2 as alpha and I will not make any announcement to the user and community lists, which already know it as alpha. In any case I think the vote is mostly moot, since 5.5.3 is coming soon and the points made in Remy's voting email are enough to convince me 5.5.2 should stay alpha anyhow. So with 5.5.2 staying where it is, when shall I cut 5.5.3? I think we would need to have the admin webapp be kinda supported for this release to be a beta, right ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/server PoolTcpConnector.java
billbarker2004/10/01 18:22:10
Modified:src/share/org/apache/tomcat/modules/server
PoolTcpConnector.java
Log:
For backwards compatability, default the strategy to leader/follower.
Revision ChangesPath
1.19 +1 -3
jakarta-tomcat/src/share/org/apache/tomcat/modules/server/PoolTcpConnector.java
Index: PoolTcpConnector.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/server/PoolTcpConnector.java,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- PoolTcpConnector.java 25 Feb 2004 07:18:35 - 1.18
+++ PoolTcpConnector.java 2 Oct 2004 01:22:10 - 1.19
@@ -58,6 +58,7 @@
public PoolTcpConnector() {
ep = new PoolTcpEndpoint();
+ ep.setStrategy(lf);
}
// Start/stop
@@ -107,9 +108,6 @@
// Pool setup
-public void setPools( boolean t ) {
- ep.setPoolOn(t);
-}
public void setMaxThreads( int maxThreads ) {
ep.setMaxThreads(maxThreads);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31465] - JSP encoding is wrong
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31465. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31465 JSP encoding is wrong [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-10-02 01:36 --- The reason for the seemly extra character in out.write() is that the java file Jasper generated is defaulted to utf8 encoding (0xa9 is 0xc2a9 in utf8). However, you cannot just set the Jasper option javaEncoding to ISO-5589-1, because you'll then also need to set a javac option to use the same encoding, and currently you cannot change the javac source encoding. Looks like the only way for this to work is to use urt8 for both the page and the response. :( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
