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=5497.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5489.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5526.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
I'm trying to figure out what I should do with the AJP binaries, as the CVS
is a bit messy at the moment (and it includes two versions of the sources).
I can:
- keep the current binary for b1
- try to upgrade, but I'd like to know which one I should use (and the build
script should be
remm01/12/20 02:00:39
Modified:catalina/src/share/org/apache/catalina/core Tag:
tomcat_40_branch StandardWrapper.java
Log:
- Port STM instance pooling, which gives STM decent performance.
Please test !
Revision ChangesPath
No
remm01/12/20 02:06:03
Modified:.Tag: tomcat_40_branch RELEASE-NOTES-4.0.2-B1.txt
Log:
- Release notes update.
Revision ChangesPath
No revision
No revision
1.1.2.6 +10 -4
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=5531.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5532.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the HEAD branch. They should run
fine on Tomcat 4.0
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=5486.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5497.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm01/12/20 04:25:07
Modified:catalina/src/share/org/apache/catalina/servlets Tag:
tomcat_40_branch DefaultServlet.java
Log:
- Fix bug 5497.
If headers will now be ignored when the default servlet is included.
Revision ChangesPath
No
remm01/12/20 04:37:02
Modified:tester/src/bin tester.xml
Log:
- Add test case for bug 5497.
Revision ChangesPath
1.80 +5 -1 jakarta-tomcat-4.0/tester/src/bin/tester.xml
Index: tester.xml
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=5535.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5486.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm01/12/20 06:07:14
Modified:tester/src/bin Tag: tomcat_40_branch tester.xml
Log:
- Add test case for bug 5497.
Revision ChangesPath
No revision
No revision
1.69.2.3 +5 -0
remm01/12/20 06:08:49
Modified:.Tag: tomcat_40_branch RELEASE-NOTES-4.0.2-B1.txt
Log:
- Release notes update.
Revision ChangesPath
No revision
No revision
1.1.2.7 +4 -4
remm01/12/20 06:09:51
Modified:webapps/ROOT Tag: tomcat_40_branch index.html
Log:
- Update version number.
Revision ChangesPath
No revision
No revision
1.29.2.6 +2 -2
remm01/12/20 06:10:22
Modified:catalina/src/share/org/apache/catalina Tag: tomcat_40_branch
Globals.java
Log:
- Update version number.
Revision ChangesPath
No revision
No revision
1.39.2.6
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=5531.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
I've finished uploading the 4.0.2-b1 binaries:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.2-b1/
All known packaging issues over 4.0.1 should have been fixed (gifs
corruption, installer not finding JDK, and probably others).
The RPMs and the connector native binaries
I'm trying to figure out what I should do with the AJP
binaries, as the CVS
is a bit messy at the moment (and it includes two versions of
the sources).
I can:
- keep the current binary for b1
- try to upgrade, but I'd like to know which one I should use
(and the build
script
Hi,
After a lot of efforts, it turns out the connectors (in
j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch
of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the HEAD branch.
They should run
fine
Hi,
We've encountered a problem with the way jk_nt_service.c creates nt
services.
Specifically, the call to CreateService uses the name passed in for the
service as both the service name and the service display name. This is a
problem because there are restrictions on the service name that do
I'm trying to figure out what I should do with the AJP
binaries, as the CVS
is a bit messy at the moment (and it includes two versions of
the sources).
I can:
- keep the current binary for b1
- try to upgrade, but I'd like to know which one I should use
(and the build
i take it all back :)
i just updated j-t-c/jk and i can't build it. and i don't have time to
try
to figure it out right now. sorry.
so, maybe it's best for now to go with the current binary.
Yes, we're in the middle of Costin's refactoring, so it's not a very good
time to upgrade.
Remy
On Thu, 20 Dec 2001, Remy Maucherat wrote:
i take it all back :)
i just updated j-t-c/jk and i can't build it. and i don't have time to
try
to figure it out right now. sorry.
so, maybe it's best for now to go with the current binary.
Yes, we're in the middle of Costin's
On Thu, 20 Dec 2001, Kevin Seguin wrote:
perhaps now is the time to do some rethinking of where the connectors for
each serlvet container live.
today, in j-t-c, there is the framework (for lack of a better word) for
connectors plus the individual connectors or adapters for tomcat 3 and
On Thu, 20 Dec 2001, Kevin Seguin wrote:
i just updated j-t-c/jk and i can't build it. and i don't have time to try
to figure it out right now. sorry.
What's broken ? I'll do a clean checkout and build, I tried few times on
my system and seemed to work fine.
Have you updated
jfclere 01/12/20 09:44:51
Modified:jk/java/org/apache/ajp/tomcat4 Ajp13Connector.java
Ajp13Processor.java
Log:
Arrange some of the 4.1 incompatibilties... Till where I am able to do it!
- Please undo if needed -
Revision ChangesPath
1.10
[EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2001, Kevin Seguin wrote:
i just updated j-t-c/jk and i can't build it. and i don't have time to try
to figure it out right now. sorry.
What's broken ? I'll do a clean checkout and build, I tried few times on
my system and seemed to work
costin 01/12/20 09:53:49
Modified:jk build.properties.sample build.xml
Log:
Few fixes to the build, now should works if you have only one container.
Revision ChangesPath
1.8 +1 -1 jakarta-tomcat-connectors/jk/build.properties.sample
Index:
costin 01/12/20 09:55:43
Modified:jk/native build.xml
jk/native2 build.xml
jk/native2/common jk_md5.c
Log:
More fixes to the build.
Revision ChangesPath
1.25 +2 -2 jakarta-tomcat-connectors/jk/native/build.xml
Index:
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=5463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5523.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5532.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
costin 01/12/20 11:30:26
Modified:jk build.properties.sample build.xml
Removed: jk/native build.properties.sample
jk/native2 build.properties.sample
Log:
Few more changes.
Consolidate all build.properties in the top dir ( so user has to change
a
costin 01/12/20 11:32:15
Added: jk/conf webapp_41.xml
Log:
The webapp descriptor ( equivalent to interceptors.xml )
( not that it'll not work at this moment, use the same mechanism for
4.1 as for 4.0 )
Revision ChangesPath
1.1
On Thu, 20 Dec 2001, Remy Maucherat wrote:
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the
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=5532.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
keith 01/12/20 11:56:44
Modified:src/share/org/apache/tomcat/modules/generators
ErrorHandler.java
Log:
The statusHandler is returning a body for 304 responses,
which is forbidden by both HTTP/1.1 and HTTP/1.0.
IE is forgiving, but Netscape Navs 6.x
keith 01/12/20 11:59:30
Modified:src/share/org/apache/tomcat/modules/generators
ErrorHandler.java
Log:
spaces - tabs
Revision ChangesPath
1.22 +4 -4
jakarta-tomcat/src/share/org/apache/tomcat/modules/generators/ErrorHandler.java
[EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2001, Kevin Seguin wrote:
perhaps now is the time to do some rethinking of where the connectors for
each serlvet container live.
today, in j-t-c, there is the framework (for lack of a better word) for
connectors plus the individual
[EMAIL PROTECTED] wrote:
Keeping all container adapters in j-t-c has the extra benefit that we
can
share more code among them.
It still feels wierd to me. Imagine if JNDI did things this way...
we'd have to have every provider installed just to build it. :)
I think if the layer of
On Thu, 20 Dec 2001, Remy Maucherat wrote:
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still
can't
be compiled against both the 4.0 branch and the HEAD branch of the
Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built
When I try to build Tomcat 4.0.1 on my system, I get the following error and
it fails:
build-main:
[javac] Compiling 93 source files to
/opt/jakarta-tomcat-4.0.1-src/jasper/build/classes
[javac]
/opt/jakarta-tomcat-4.0.1-src/jasper/src/share/org/apache/jasper/compiler/Pa
On Thu, 20 Dec 2001, Paul Speed wrote:
My thinking ( for 4.1/3.3 ) was to have j-t-c built as a
'standalone module', a trusted/priviledged webapp that can be deployed and
is self-contained.
Keeping all container adapters in j-t-c has the extra benefit that we can
share more code
remm01/12/20 12:51:40
Modified:jk/java/org/apache/jk/server/tomcat40 Ajp13Connector.java
Ajp13Processor.java
Log:
- Also add the new findLifecycleListeners in the new jk.server.tomcat40 package
(what's the difference with o.a.ajp.tomcat4, btw ?).
remm01/12/20 13:25:23
Modified:catalina/src/share/org/apache/catalina Connector.java
catalina/src/share/org/apache/catalina/connector/http
HttpConnector.java
catalina/src/share/org/apache/catalina/connector/http10
remm01/12/20 13:19:54
Modified:catalina/src/share/org/apache/catalina Tag: tomcat_40_branch
Globals.java
Log:
- Update version number.
Revision ChangesPath
No revision
No revision
1.39.2.7
remm01/12/20 13:20:09
Modified:webapps/ROOT Tag: tomcat_40_branch index.html
Log:
- Update version number.
Revision ChangesPath
No revision
No revision
1.29.2.7 +1 -1
A 4.x person might want to take a look to make sure this
doesn't happen there, too. The performance and stability
of Netscape is like night and day with this...
Keith
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 20, 2001 2:57 PM
To:
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=5497.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5486.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
A 4.x person might want to take a look to make sure this
doesn't happen there, too.
It doesn't.
GET /index.html HTTP/1.1
Host: localhost
If-modified-since: Thu, 20 Dec 2001 21:37:49 GMT
HTTP/1.1 304 Not Modified
Date: Thu, 20 Dec 2001 21:40:01 GMT
Server: Apache Tomcat/4.1-dev (HTTP/1.1
On 20 Dec 2001 [EMAIL PROTECTED] wrote:
Modified:jk/java/org/apache/jk/server/tomcat40 Ajp13Connector.java
Ajp13Processor.java
Log:
- Also add the new findLifecycleListeners in the new jk.server.tomcat40 package
(what's the difference with
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=5449.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=5549.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
61 matches
Mail list logo