[Coyote] Coyote 1.0 Beta 4 available

Coyote 1.0 Beta 4 is now available, and includes: - A high performance HTTP/1.1 processor - An adapter for Tomcat 3.3.x - An adapter for Tomcat 4.0.x Changes over Beta 3 include: - Support for HTTP/1.1 expectations in Tomcat 3.3. - Optimized cookie parsing in Tomcat 4. - Other minor changes. Bin

cvs commit: jakarta-tomcat-4.0/lib tomcat-coyote.jar tomcat-http11.jar tomcat-util.jar

remm02/03/22 19:30:37 Modified:lib Tag: tomcat_40_branch tomcat-util.jar Added: lib Tag: tomcat_40_branch tomcat-coyote.jar tomcat-http11.jar Log: - Adding the Coyote 1.0b4 binaries. Revision ChangesPath No

cvs commit: jakarta-tomcat/src/webpages index.html

larryi 02/03/22 19:08:45 Modified:src/webpages index.html Log: Update for 3.3.1 Final Revision ChangesPath 1.26 +2 -2 jakarta-tomcat/src/webpages/index.html Index: index.html === RCS file

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core ContextManager.java

larryi 02/03/22 19:08:24 Modified:src/share/org/apache/tomcat/core ContextManager.java Log: Update for 3.3.1 Final Revision ChangesPath 1.204 +1 -1 jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java Index: ContextManager.java ==

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/generators ErrorHandler.java

larryi 02/03/22 18:45:52 Modified:src/share/org/apache/tomcat/modules/generators ErrorHandler.java Log: Include message if present in NotFoundHander response. Submitted by: David Schreibman Revision ChangesPath 1.26 +7 -0 jakarta-

[FAQ] jGuru FAQ Update

jGuru maintains FAQs and Forums on Servlets, JSP, and Tomcat (as well as many other Java topics). Here is an automated update on recent postings to Tomcat-related FAQs. Please direct flames and feedback to [EMAIL PROTECTED] . - Alex ++ JavaServer Pages (JSP) FAQ: http://www.jguru.com/faq/JSP

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_serialize_ajp.c

costin 02/03/22 16:15:44 Removed: jk/native2/common jk_serialize_ajp.c Log: Remove it - the code has been moved to better places, the API where it's used ( it's just adding/extracting params from the msg ), the protocol is only in jk_msg. -- To unsubscribe, e-mail:

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4 CoyoteConnector.java

remm02/03/22 15:58:27 Modified:coyote/src/java/org/apache/coyote/tomcat4 CoyoteConnector.java Log: - Remove unused 'allowChunking' flag. The HTTP/1.1 processor has a different mechanism to handle non-compliant clients, but it is not exposed at the mom

RE: Jk2 docs

On Sat, 23 Mar 2002, GOMEZ Henri wrote: > >I documented 2 properties, to be used to override the default > >when new protocols/apis are added: > > > > channel.socket.local.protocol=ajp13 ( it could be WARP, or IIOP or RPC ) > > ok, that's what I looked for > > > channel.socket.local.api=ajp13 (

RE: Jk2 docs

>> channel.socket.local.type=ajp13 ? > >No :-) > >The only protocol that we support in Jk at this moment is the >ajp13 protocol ( lb, status, etc are workers, but not protocols ), >so it is the default and users don't have to set it explicitely. > >I documented 2 properties, to be used to override

RE: Jk2 docs

On Fri, 22 Mar 2002, GOMEZ Henri wrote: > >channel.socket.local.port=8009 > >channel.socket.local.lbfactor=1 > >channel.socket.local.secretkey=... > > good, a channel indicate transport, > a worker should be a layer upper, it use a channel > for transport and channel could be virtual (ie lb)

RE: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

>> Tomcat 4.0.4 Beta 2 release: +1 (rpms) >> Inclusion of the Coyote binaries: >> >> +1 [X] Yes >> -1 [ ] No >> I'd like to have Coyote source instead -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

yes, read my comment in : http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-Or

RE: Jk2 docs

>What the user most define are the communication channels ( host, port, >etc ). It is far cleaner to set the properties on the channel and use >defaults for the handler. > >Henri - is this solution acceptable ? > >That means: > >channel.socket.local.port=8009 >channel.socket.local.lbfactor=1 >ch

RE: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

I wrote such a note : http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 And recalled in my comment to read also your analyze in bug #5181 I closed bug #7177 since it's a really old known problems allready reported and explained for TC 3.2/3.3 We urgently need a sort of FAQ in JTC -

DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/realm DeleteRealmAction.java SaveUserDatabaseRealmAction.java UserDatabaseRealmForm.java

manveen 02/03/22 13:45:08 Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin Lists.java TomcatTreeBuilder.java webapps/admin/WEB-INF/classes/org/apache/webapp/admin/host EditHostAction.java SaveHostAction.java

DO NOT REPLY [Bug 7374] - Apache Tomcat/4.0.1 message on standard output

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7374] New: - Apache Tomcat/4.0.1 message on standard output

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Jk2 docs

Hi, I just checked in 2 docs for jk2, one describing the general model and one start of the config manual. It's obviously subject to change. I think I found a solution to address Henri's comments about worker/channel configuration - that is to reverse things. "Worker" is an extremely confus

[PATCH] TC3.3.1 sendError(404, msg) ignores msg

Short version: Here's a patch that modifies the NotFoundHandler to incorporate the msg from sendError(sc, msg) into the html response body. Currently, the passed in msg is ignored. Long version: I know the servlet spec lets the server decide what the response body will contain, and I k

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

On Fri, 22 Mar 2002, Remy Maucherat wrote: > > > below). The Coyote connector will *not* be enabled by default, but will > > > appear commented out in the default server.xml configuration file. > > > > +1 on enabling it by default, commenting out the old connector. > > I didn't propose to do tha

DO NOT REPLY [Bug 7371] - error-page directive not kicking in for errors thrown from servlets

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-connectors/jk/doc/jk2 config.html jk2.html

costin 02/03/22 12:49:53 Added: jk/doc/jk2 config.html jk2.html Log: Added an initial documentation for the new jk2 design and an initial documentation for the default config. PLEASE, REVIEW ! Revision ChangesPath 1.1 jakarta-tomcat-connectors/

DO NOT REPLY [Bug 7371] New: - error-page directive not kicking in for errors thrown from servlets

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

It's the same issue in 3.3.x (This part of mod_jk is common to both). - Original Message - From: "Hans Schmid" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 8:13 AM Subject: AW: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

> > below). The Coyote connector will *not* be enabled by default, but will > > appear commented out in the default server.xml configuration file. > > +1 on enabling it by default, commenting out the old connector. I didn't propose to do that, because, although the new connector appears robust an

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans MBeanFactory.java MBeanUtils.java

amyroh 02/03/22 11:27:27 Modified:catalina/src/share/org/apache/catalina/mbeans MBeanFactory.java MBeanUtils.java Log: Fix createObjectName for Host. It should be "host=" instead of "name=". Revision ChangesPath 1.20 +8 -8 jakarta-tom

Re: bug in catalina.sh

Fabien, Since the "$@" is necessary to preserve quoting of arguments with spaces in them, changing it to $@ is not a really good solution. First off, which Unix platform are you using? I know that the "$@" works on Solaris and Linux and Mac OS X. Also, have you tried using "${@}"? Most platfroms

bug in catalina.sh

Hello, I noticed a bug in catalina.sh that make some of us have problem starting tomcat. The common error is that a message usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [ -debug ] [ -nonaming ] { start | stop } is printed in $CATALINA_HOME/logs/catalina.out I began

DO NOT REPLY [Bug 7369] New: - HttpSession.setMaxInactiveInterval takes minutes instead of seconds.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/res StringManager.java

larryi 02/03/22 10:46:30 Modified:util/java/org/apache/tomcat/util/res StringManager.java Log: Finish sync'ing to Tomcat 3.3.x code. The code for j-t-c and j-t util classes are now the same, though minor source differences remain. Revision ChangesPath 1.2 +21 -

DO NOT REPLY [Bug 4829] - Automatic deployment of war files does not work properly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

> I also plan to make a Coyote 1.0 beta 4 at the same time, to pick up the > bugfixes and minor improvements in the Tomcat adaptors. > > Tomcat 4.0.4 Beta 2 release: > > +1 [*] I support the release, and I will help > +0 [ ] I support the release > -0 [ ] I don't support the release > -1 [ ] I'm

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

+1 on both. > Date: Thu, 21 Mar 2002 16:25:50 -0800 > From: Remy Maucherat <[EMAIL PROTECTED]> > Subject: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release > To: Tomcat Developers List <[EMAIL PROTECTED]> > MIME-version: 1.0 > X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600. > Conten

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

> > Tomcat 4.0.4 Beta 2 release: > > +1 [X] I support the release, and I will help > +0 [ ] I support the release > -0 [ ] I don't support the release > -1 [ ] I'm against the release because: > > > > Inclusion of the Coyote binaries: > > +1 [X] Yes > -1 [ ] No > > > My vote is +1 for both

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

On Thu, 21 Mar 2002, Remy Maucherat wrote: > below). The Coyote connector will *not* be enabled by default, but will > appear commented out in the default server.xml configuration file. +1 on enabling it by default, commenting out the old connector. > I also plan to make a Coyote 1.0 beta 4 at

RE: Entity in web.xml

The first message, XmlMapper: Can't find resource for entity: jspdecl --> /var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml "null" is irrelevant. It only tells you Tomcat has no cached entity for the specified public identifier. You know, Tomcat actually caches entities for some well known public iden

RE: Entity in web.xml

Well, it still doesn't works :( Now I got: XmlMapper: Can't find resource for entity: jspdecl --> /var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml "null" PARSE error at line 0 column 0 org.xml.sax.SAXParseException: File "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml" not found. Thank you for your

RE: Entity in web.xml

Try declaring your ENTITY using a public identifier: This works for me altough I've only used Tomcat 3.x versions this far. Cheers, Attila. > -Original Message- > From: Benoit Mahe [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 22, 2002 10:49 AM > To: Szegedi, Attila; > Cc: Benoit

Entity in web.xml

Hello, I'm trying to use entity in web.xml for tomcat 4.0.3, but it doesn't work: Here is my web.xml: http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"; [ ]> &jspdecl; But when tomcat starts, I got an exception: 2002-03-22 09:39:42 ContextConfig[] Parse error in application web.xml ja

Re: Servlet wierd behaviour regarding concurrency in tomcat 4.0.1

I see the same results in tomcat 4.0.2 and in jetty 3.1.3-1. DO I MISS SOMETHING??? Help!!! Is it ALWAYS that 2 requests for the SAME URI block I seem to raise the white flag fellas. If anybody can shed some light please do. In specs, discussions i have never seen any notion of t

Servlet wierd threading behaviour in tomcat 4.0.1

Hi, firstoff my excuses for posting to the developer list, but unfortunately user-list didnt shed some light on the issue. So here it is :) I have seen a strange threading behaviour in catalina engine. For servlets that a) Dont implement SingleThreadModel b) Dont synchronize over resources c) Do

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

> I have to commit and retest things (PR6982) and properties problems with Coyote > as soon as I am thru +1 for both. Ok. Properties means message strings ? If so, yes, I'd say it needs to be improved. Remy -- To unsubscribe, e-mail: For additional commands, e-mail

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

Remy Maucherat wrote: > I'd like to propose releasing 4.0.4 beta 2 within a few days (friday at the > earliest, next tuesday at the latest). This release will include bugfixes > (the list is in the usual release notes document in CVS) as well as the > inclusion of the Coyote binaries (conditional

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7366] New: - ISAPI Redirector Replacement

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7359] - Classloader problems with RMI

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

AW: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

Hi, what about Tomcat 3.3 ? Does this correspond to Ajp13Connector maxThreads >= the maxiumum number of Apache httpd processes in this case? Thanks, Hans > -Ursprungliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im > Auftrag von Glenn Nielsen > Gesendet: Freitag, 2

DO NOT REPLY [Bug 7364] New: - compiler creates empty .java files for invalid URLs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

> -Original Message- > From: Remy Maucherat [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 21, 2002 7:26 PM > To: Tomcat Developers List > Subject: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release > > > I'd like to propose releasing 4.0.4 beta 2 within a few days > (friday

Re: tomcat 4.0.3 + mod_jk

GOMEZ Henri wrote: >>Up to now i Worked only on jk from JTC, but if we get the same >>functionality from jk2 I could have a look at it. I thought >>that jk2 was >>for apache2. But I may misunderstound this. > > > jk2 is the reworked jk, for ap 1.3/2.0, IIS/iPlanet to come > ok, for which sh

RE: tomcat 4.0.3 + mod_jk

>Up to now i Worked only on jk from JTC, but if we get the same >functionality from jk2 I could have a look at it. I thought >that jk2 was >for apache2. But I may misunderstound this. jk2 is the reworked jk, for ap 1.3/2.0, IIS/iPlanet to come -- To unsubscribe, e-mail:

Re: tomcat 4.0.3 + mod_jk

GOMEZ Henri wrote: >>Yes. Costin suggested to use a special lb-factor. I would use >>-1 for the >>lb-factor. But this wouldn't solve the problem if someone set >>more than >>one worker to this value. To use a new config tag for >>optionally setting >>a default worker would be a cleaner way.

RE: tomcat 4.0.3 + mod_jk

>Yes. Costin suggested to use a special lb-factor. I would use >-1 for the >lb-factor. But this wouldn't solve the problem if someone set >more than >one worker to this value. To use a new config tag for >optionally setting >a default worker would be a cleaner way. And it would be easier to

DO NOT REPLY [Bug 7360] New: - res-sharing-scope not supported

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7359] New: - Classloader problems with RMI

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: tomcat 4.0.3 + mod_jk

GOMEZ Henri wrote: yes, I know. But when I come in without a session the function get_most_suitable_worker in jk_lb_worker.c will find a >>> >>worker by using >> the lb-factor and do weighted round robin. And at this >>> >>position I would >> like to switch off the load-balanc

RE: tomcat 4.0.3 + mod_jk

>My thinking for jk2 was that the session stickiness should go >in front of >everything, and be enabled by default, independent of lb. Agreed. May be we could build a more powerfull system later with a reworker LB supporting failure via JTC cluster. -- To unsubscribe, e-mail:

RE: tomcat 4.0.3 + mod_jk

>>>yes, I know. But when I come in without a session the function >>>get_most_suitable_worker in jk_lb_worker.c will find a >worker by using >>>the lb-factor and do weighted round robin. And at this >position I would >>>like to switch off the load-balancing and select the worker which is >>