DO NOT REPLY [Bug 9931] - Base64 decoder chokes on a whitespace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9931. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9931 Base64 decoder chokes on a whitespace --- Additional Comments From [EMAIL PROTECTED] 2002-09-28 08:45 --- Well MIME RFC is a governing standard for most base64 implementations: http://www.faqs.org/rfcs/rfc2045.html On a page 27 the recomend folding at 76th column and ignoring newlines. That would be enough for interoperability with Python's xmlrpclib. However for max interoperability I think all whitespace should be silently ignored ( \t\r\n) (tabs and spaces can be inserted by XML formatters at a begining of line) and exception should be throwed if character outside base64 chars and whitespace is found. Current impl (I haven't checked CVS recently) decodes base64 encoded binary with newlines at 76th column into a slightly larger and distinctly different binary without raising any exceptions. I find it some how unusable so I've replaced it with oreilly's base64 decored -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [ANNOUNCEMENT]: JK 1.2.0 is now available
Just compiled and tested mod_jk 1.2.0 from CVS, Apache 2.0.42. Seems as solid as ever... Good stuff! Bojan On Sat, 2002-09-28 at 01:03, Henri Gomez wrote: Hi all, The Jakarta-Tomcat-Connector team is pleased to announce the availability of JK 1.2.0. JK, also known as mod_jk, is a Tomcat / WebServers plug-in that handles the communication between Tomcat and webservers. Currently Apache 1.3.x and 2.0.x, IIS, Netscape/iPlanet are supported. binaries and source versions of the release are available and can be downloaded from : http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/ Binaries allready available are : - Linux i386 (Apache 1.3/2.0.42) - Solaris 8 (Apache 1.3/2.0.39/2.0.42) - Win32 (IIS/Apache 1.3/2.0.42) MacOS X, AIX, iSeries binaries to be released shortly (I hope) Feel free to contact us to provide binaries for your own operating system. Enjoy! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13089] - Coyote sources are missing from the source zip for Tomcat 4.1.12
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13089. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13089 Coyote sources are missing from the source zip for Tomcat 4.1.12 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-09-28 12:58 --- They are in the jakarta-tomcat-conectors zip. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: fault-tolerance
Kirill Koulechov wrote: Hi, i think i have a rather simple questions for the developers of tomcat. Let me give short explanation. I am working on a research topic, which is generic fault detection and tolerance for software architectures. i've picked apache as a sample of c/c++ program and tomcat as a java program. don't get me wrong: i did it because i beleave that these programs are well known, and developed professionaly, since i need fault statistics that are not obscured by simply omitting basic rules of software development. i studied the bug database for tomcat4 versions 4.0.x Final, with the assumption that these have been (fairly) stable versions. i omitted NEW and UNCONFIRMED bugs, as well as INVALID, WONTFIX, DUPLICATE, WORKSFORME. besides that, i ignored some IMHO rare plattforms like BeOS, OS/2, Netware, OS/400 and included only critical, major and normal bugs. i did that in the hope to get representative statistics about common software faults in a big, professionaly developed software product. if i did something wrong, please correct me. at the end i got 163 bugs. now the important stuff. after examining some of them, i noticed some amount of bugs (i.e. bugs #4930, #4047) causing unchecked exceptions, which strike all the way through the stack, ending in org.apache.catalina.connector.http.HttpProcessor.run() and then in java.lang.Thread.run(). in my understanding, this stops the affected thread and all functionality that was done by org.apache.catalina.connector.http.HttpProcessor.run() is unavailable now. what is tomcats reaction to this? does the program crash/freeze/hang whatever, or do these exceptions not affect the runime behaviour? or is only the active servlet affected? besides that, i wondered what are the effects of the bugs 3817, 4542, 5201, since the provided stack doesn't go up to java.lang.Thread.run(). thank you very much in advance, i really appreciate your answers because it doesnt help you developing tomcat in the first place, but just think that you are helping to research ways to prevent software from crashing at all! I did some work to improve that on the old HTTP/1.1 connector since then. This connector won't be maintained anymore, unless a critical security problem is found (I hope not). On Coyote HTTP/1.1, I took extra care to make everything rock solid in terms of exception handling and algorithms (as well as fast, but we're talking about reliability here). Feel free to review it. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Question about Internationalization
Hi, I tested a GB2312-based JSP page on Tomcat 4.1.12, and it worked fine. (The attached file). It shows ni-hao-ma in simplified Chinese character system and the response encoding, i.e. GB2312. The key point I'd like to make clear is that encoding of a JSP page should keep up with that of response that the page generates for the best delivery of content, in particular, under non-latin-1 character sets. This concept is actually introduced to JSP 2.0 spec explicitly with JSP configuration feature. I believe localization issues will be smoothly gone with Tomcat 5 and other containers compliant with JSP 2 style. P.S. a tech-tip for page encoding: Dreamweaver helps adjust page encoding to a specific character set, such as EUC-KR, and certainly GB2312. (I did this with Dreamweaver MX although I use Windows XP Korean version.) -Original Message- From: Steve Chai [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 2:11 AM To: [EMAIL PROTECTED] Subject: Question about Internationalization Hi, I am using Tomcat 4.1 now. I got the internationalization problem. In my jsps, the charset is set to gb2312, which is for chinese, but the chinese character can not show up correctly. These jsps are running very well in Tomcat 4.0.4. However after I did the following replacement, they are also running well in Tomcat 4.1. What I did is: In Tomcat 4.1\common\lib folder, just simply replace jasper-compiler.jar jasper-runtime.jar and servlet.jar with Tomcat 4.0.4 version's. Then it works well. Is it a bug ? or I have to config something in Tomcat 4.1 for Internationalization. Please give me feedback. Thanks Steve Cai _ Chat with friends online, try MSN Messenger: http://messenger.msn.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] test.jsp Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.xml tomcat.nsi
remm2002/09/28 06:47:43
Modified:.build.xml tomcat.nsi
Log:
- Fix and unify source package.
- Update installer script.
Revision ChangesPath
1.35 +70 -65jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- build.xml 18 Sep 2002 13:03:36 - 1.34
+++ build.xml 28 Sep 2002 13:47:43 - 1.35
@@ -16,19 +16,25 @@
property name=project value=jakarta-tomcat /
property name=final.namevalue=${project}-${version} /
property name=final-src.namevalue=${project}-${version}-src /
+
+ !-- Subprojects --
+ property name=api.project value=jakarta-servletapi-5 /
+ property name=tomcat.projectvalue=jakarta-tomcat-5 /
+ property name=catalina.project value=jakarta-tomcat-catalina /
property name=jtc.project value=jakarta-tomcat-connectors /
- property name=jtc.final.namevalue=${jtc.project}-${version} /
- property name=jtc.final-src.namevalue=${jtc.project}-${version}-src /
+ property name=jasper.projectvalue=jakarta-tomcat-jasper /
!-- Source dependencies --
property name=api.home
- value=${basedir}/../jakarta-servletapi-5/
- property name=catalina.home
- value=${basedir}/../jakarta-tomcat-catalina/
+ value=${basedir}/../${api.project}/
+ property name=catalina.home
+ value=${basedir}/../${catalina.project}/
property name=jasper.home
- value=${basedir}/../jakarta-tomcat-jasper/jasper2/
+ value=${basedir}/../${jasper.project}/jasper2/
property name=jtc.home
- value=${basedir}/../jakarta-tomcat-connectors/
+ value=${basedir}/../${jtc.project}/
+ property name=tomcat.home
+ value=${basedir}/../${tomcat.project}/
!-- Build Defaults --
property name=catalina.build value=${catalina.home}/build/
@@ -322,31 +328,60 @@
!-- == DIST: Create Sources --
target name=dist-source
+
mkdir dir=${tomcat.dist}/src/
-copy todir=${tomcat.dist}/src
+mkdir dir=${tomcat.dist}/src/${api.project}/
+mkdir dir=${tomcat.dist}/src/${tomcat.project}/
+mkdir dir=${tomcat.dist}/src/${catalina.project}/
+mkdir dir=${tomcat.dist}/src/${jtc.project}/
+mkdir dir=${tomcat.dist}/src/${jasper.project}/
+mkdir dir=${tomcat.dist}/src/${jasper.project}/jasper2/
+
+!-- jakarta-tomcat-5 source --
+copy todir=${tomcat.dist}/src/${tomcat.project}
fileset dir=${basedir}
exclude name=**/build/**/
exclude name=**/dist/**/
-exclude name=jasper/**/
exclude name=build.properties/
/fileset
/copy
-mkdir dir=${tomcat.dist}/src/catalina/
-copy todir=${tomcat.dist}/src/catalina
- fileset dir=${catalina.home}/
-/copy
-mkdir dir=${tomcat.dist}/src/jasper/
-copy todir=${tomcat.dist}/src/jasper
- fileset dir=${jasper.home}/
+
+!-- jakarta-servletapi-5 source --
+copy todir=${tomcat.dist}/src/${api.project}
+ fileset dir=${api.home}
+include name=jsr154/**/
+include name=jsr152/**/
+exclude name=**/build/**/
+exclude name=**/dist/**/
+exclude name=build.properties/
+ /fileset
+/copy
+
+!-- jakarta-tomcat-5 source --
+copy todir=${tomcat.dist}/src/${catalina.project}
+ fileset dir=${catalina.home}
+exclude name=**/build/**/
+exclude name=**/dist/**/
+ /fileset
/copy
-mkdir dir=${tomcat.dist}/jtc-src/
-copy todir=${tomcat.dist}/jtc-src
+
+!-- jakarta-tomcat-jasper source --
+copy todir=${tomcat.dist}/src/${jasper.project}/jasper2
+ fileset dir=${jasper.home}
+exclude name=**/build/**/
+exclude name=**/dist/**/
+ /fileset
+/copy
+
+!-- jakarta-tomcat-connectors source --
+copy todir=${tomcat.dist}/src/${jtc.project}
fileset dir=${jtc.home}
exclude name=coyote/build/**/
exclude name=http11/build/**/
exclude name=jk/build/**/
exclude name=util/build/**/
-exclude name=webapp/build/**/
+exclude name=webapp/**/
+exclude name=lib/**/
exclude name=build.properties/
/fileset
/copy
@@ -487,11 +522,6 @@
zip zipfile=${tomcat.dist}/${final-src.name}.zip
zipfileset dir=${tomcat.dist}/src prefix=${final-src.name} /
/zip
-!-- Package JTC Source --
-zip zipfile=${tomcat.dist}/${jtc.final-src.name}.zip
- zipfileset dir=${tomcat.dist}/jtc-src
-
cvs commit: jakarta-tomcat-catalina/catalina/src/conf server-noexamples.xml.config
remm2002/09/28 06:47:57 Removed: catalina/src/conf server-noexamples.xml.config Log: - Remove useless file. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[VOTE] [5.0] Milestones
Hi, Now that the first stable releases of Tomcat 4.1 are out (and according to reports, of good overall quality), it could be appropriate to start releasing 5.0.x milestones. It should be pointed out that 5.0.x is still far from being feature complete (esp the configuration code needs to be unified if possible, and some optimizations are needed), so the milestones should be considered alpha or pre alpha until further notice. ballot [ ] +1 Yes, start releasing milestones [ ] -1 No, because: /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] [5.0] Milestones
I wish Tomcat 5 would be available as soon as possible. Thank those who have been developing it very much. Here's my vote: -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Saturday, September 28, 2002 11:12 PM To: Tomcat Developers List Subject: [VOTE] [5.0] Milestones Hi, Now that the first stable releases of Tomcat 4.1 are out (and according to reports, of good overall quality), it could be appropriate to start releasing 5.0.x milestones. It should be pointed out that 5.0.x is still far from being feature complete (esp the configuration code needs to be unified if possible, and some optimizations are needed), so the milestones should be considered alpha or pre alpha until further notice. ballot [X] +1 Yes, start releasing milestones [ ] -1 No, because: /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13110] New: - scriptlets around jsp:param fail
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13110.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13110
scriptlets around jsp:param fail
Summary: scriptlets around jsp:param fail
Product: Tomcat 4
Version: 4.1.12
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I'm not sure, but
can't find anything in the specs wich wouldn't allow:
jsp:forward page=test.jsp
% if (true) {
%
jsp:param name=param value=5/
% }
%
/jsp:forward
this will produce
Expected param tag with name and value attributes without the params tag
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_channel_socket.c
nacho 2002/09/28 13:06:19
Modified:jk/native2/common jk_channel_socket.c
Log:
Reverted a prior fix, it seems that hangs w2k IIS, it's starts to stuck threads in
this loop until exhausted or max connections reached..
Revision ChangesPath
1.41 +3 -4 jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c
Index: jk_channel_socket.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- jk_channel_socket.c 24 Sep 2002 22:36:28 - 1.40
+++ jk_channel_socket.c 28 Sep 2002 20:06:19 - 1.41
@@ -328,12 +328,11 @@
#ifdef WIN32
if(SOCKET_ERROR == ret) {
-errno = WSAGetLastError();
+errno = WSAGetLastError() - WSABASEERR;
}
-} while (ret == -1 errno == WSAECONNREFUSED);
-#else
-} while (-1 == ret EINTR == errno);
#endif /* WIN32 */
+
+} while (-1 == ret EINTR == errno);
/* Check if we connected */
if(ret != 0 ) {
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] [5.0] Milestones
+1 Amy Remy Maucherat wrote: Hi, Now that the first stable releases of Tomcat 4.1 are out (and according to reports, of good overall quality), it could be appropriate to start releasing 5.0.x milestones. It should be pointed out that 5.0.x is still far from being feature complete (esp the configuration code needs to be unified if possible, and some optimizations are needed), so the milestones should be considered alpha or pre alpha until further notice. ballot [ ] +1 Yes, start releasing milestones [ ] -1 No, because: /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_channel_socket.c
The comment is wrong, the problem is with the loadbalancer logic, if one
of the configured instances got lost, connect returns WSAECONNREFUSED,
with Malden's patch, the thread gots stuck in a loop trying to connectto
a non existing tc instance..
Incidentally i have this config to test tc4 in port 8019 and tc33 in
8009, i normally dont have the 2 versions working at the same time, so i
continually get WSAECONNREFUSED.. hence the problem..
Saludos ,
Ignacio J. Ortega
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: 28 de septiembre de 2002 22:06
Para: [EMAIL PROTECTED]
Asunto: cvs commit: jakarta-tomcat-connectors/jk/native2/common
jk_channel_socket.c
nacho 2002/09/28 13:06:19
Modified:jk/native2/common jk_channel_socket.c
Log:
Reverted a prior fix, it seems that hangs w2k IIS, it's
starts to stuck threads in this loop until exhausted or max
connections reached..
Revision ChangesPath
1.41 +3 -4
jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c
Index: jk_channel_socket.c
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_chann
el_socket.c,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- jk_channel_socket.c 24 Sep 2002 22:36:28 - 1.40
+++ jk_channel_socket.c 28 Sep 2002 20:06:19 - 1.41
@@ -328,12 +328,11 @@
#ifdef WIN32
if(SOCKET_ERROR == ret) {
-errno = WSAGetLastError();
+errno = WSAGetLastError() - WSABASEERR;
}
-} while (ret == -1 errno == WSAECONNREFUSED);
-#else
-} while (-1 == ret EINTR == errno);
#endif /* WIN32 */
+
+} while (-1 == ret EINTR == errno);
/* Check if we connected */
if(ret != 0 ) {
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] [5.0] Milestones
ballot +1 /ballot -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Realm implementation question
Please forgive me if this is an obvious newbie question, but I am not a Java
guru, nor have I studied all the intricacies of Tomcat.
I am trying to implement a new Realm, which will obviously require some
configuration parameters in server.xml, and I want to make sure I understand
how to access those config parameters from within my implementation.
I can see that o.a.c.Catalina.java creates an o.a.commons.digester.Digester
that parses the server.xml file. Is it the case that the Digester will
instantiate a Realm object of the type specfied in the className attribute
of the Realm tag in the server.xml file, and initialize that object's
members using the Realm tag's attributes of the same name? So all I need
to do is write my Realm implementation with accessors and mutators for each
Realm tag attribute?
So a Realm config that looks like this:
Realm class=org.apache.catalina.realm.MyRealm propOne=foo /
would require a Realm implementation like so:
String propOne = null;
public String getPropOne() {
return this.propOne;
}
public void setPropOne(String prop) {
this.propOne = prop;
}
Am I missing anything?
Thanks in advance,
Chris
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_channel_socket.c
-Original Message- From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]] The comment is wrong, the problem is with the loadbalancer logic, if one of the configured instances got lost, connect returns WSAECONNREFUSED, with Malden's patch, the thread gots stuck in a loop trying to connectto a non existing tc instance.. Like I said you don't know if its non existing or just refusing more connections due to maximum connections reached. So what we need here is timout check inside connection phase, and not giving up on the first failed connection request. On the high load this will give you lots of 404's that are simply caused by the fact that the TC is too busy refusing more concurent connections. Incidentally i have this config to test tc4 in port 8019 and tc33 in 8009, i normally dont have the 2 versions working at the same time, so i continually get WSAECONNREFUSED.. hence the problem.. If we put the timeout check inside the connection phase of the socket, after that time we could mark the worker as disabled, or skip the timeout testing for this worker, failing on the first connection error. If the connection gets valid again, then we can check the timeout over again. MT. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6617] - Iterating over session attribute name enumeration fails with a ConcurrentModificationException on org.apache.catalina.util.Enumerator.nextElement(Enumerator.java:166);
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6617. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6617 Iterating over session attribute name enumeration fails with a ConcurrentModificationException on org.apache.catalina.util.Enumerator.nextElement(Enumerator.java:166); --- Additional Comments From [EMAIL PROTECTED] 2002-09-29 06:02 --- It looks like that the Enumeration its cached by the server , for me this is a bug because after obtaining the enumeration of the attributes i understand that its totally disconnected from Collection who creates them (probably im wrong). But i test that code in other servers and work , probably the server returns a clone. Carlos arana -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
