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=11379.
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=14077.
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=14077.
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=14059.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Costin Manolache wrote:
Remy Maucherat wrote:
A new test milestone of Tomcat 4.1 has just been released. Please help
test this upcoming Tomcat release for compliance issues and other
problems.
Downloads:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.14/
Significant changes
Henri Gomez wrote:
Mladen Turk wrote:
-Original Message-
From: news [mailto:news;main.gmane.org] On Behalf Of Costin Manolache
Sent: Monday, October 28, 2002 6:40 PM
To: [EMAIL PROTECTED]
Subject: Re: JkRequestLogFormat for JK 1.2.x on Apache 2.0 ?
Henri Gomez wrote:
I added
Henri Gomez wrote:
Henri Gomez wrote:
Did someone try to port 'JkRequestLogFormat' to Apache 2.0 ?
For instance I wonder about :
ap_bgetopt(r-connection-client, BO_BYTECT, bs);
I added 'JkRequestLogFormat' for Apache 2.0.
Great!
Glenn could you take a look ?
I don't have
Pier Fumagalli wrote:
On 29/10/02 22:46, Costin Manolache [EMAIL PROTECTED] wrote:
Remy Maucherat wrote:
A new test milestone of Tomcat 4.1 has just been released. Please help
test this upcoming Tomcat release for compliance issues and other
problems.
Downloads:
Glenn Nielsen wrote:
Henri Gomez wrote:
Mladen Turk wrote:
-Original Message-
From: news [mailto:news;main.gmane.org] On Behalf Of Costin Manolache
Sent: Monday, October 28, 2002 6:40 PM
To: [EMAIL PROTECTED]
Subject: Re: JkRequestLogFormat for JK 1.2.x on Apache 2.0 ?
Henri Gomez
It is explicitly forbidden for an include to change the headers (including
content-type). Your servlet needs to do a
response.setContentType(text/html; charset=windows-1253) before doing the
include.
Alternatively, for the servlet below, consider doing a forward instead of
an include.
Holger
This is a known problem (but it is only that it is taking time to fill the
log files). Upgrade to 4.1.14 to fix.
Chakradhar Tallam [EMAIL PROTECTED] wrote in message
news:11A60EF518EFD311962E0010B5092C17AE1043;EXCHANGE...
hi there,
we got a web application running on production system. it
I have been looking at the webClassLoader Code. I realised that the Classloader
doesnot allow the Xerces lib to be loaded from the WEB-INB/lib .
It prevents the same be filtering the org.apache.xerces package.
It means the documentation that , Application can use there on version of
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=14086.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On 30/10/02 9:19 am, Henri Gomez [EMAIL PROTECTED] wrote:
ALL directories need to be 755 (therefore only THOSE and NOT THE FILES need
to have the +x bit set) they need to look like drwxrwxr-x
Why 755 on directory ? Shouldn't they be 775 to allow group member to
update them ?
Oh, mefuck...
I think the answer is no -- you should recompile all JSPs. Would defo be
the safest option anyway.
Eddie Ruvinsky wrote:
Resending this. Does anyone happen to know the answer
to this? Is this supported?
Thanks in advance,
Eddie
--- Eddie Ruvinsky [EMAIL PROTECTED] wrote:
In Tomcat 4.1.x,
Hi all,
Just some thoughts.
I've been using the 3.3.1 release for quite some time in a
mod_jk/apache/linux kind of setup and all was fine. Though a couple of
weeks ago I felt a need to start looking at new versions of all my
API's/products in order to make sure I stay on top of things and don't
On 29/10/02 11:35 pm, Pier Fumagalli [EMAIL PROTECTED] wrote:
On 29/10/02 23:02, Mike Anderson [EMAIL PROTECTED] wrote:
DOH!
Sorry. Thats what you get when you get a Non-Unix weanie to play around on a
Unix box. I knew that I've had to do this in the past but completely spaced
it for
Just to add to previous posting i was looking at 4.1.12 source code released.
[EMAIL PROTECTED] 10/30/02 04:18PM
I have been looking at the webClassLoader Code. I realised that the Classloader
doesnot allow the Xerces lib to be loaded from the WEB-INB/lib .
It prevents the same be
I'd like to see this, even if it's just posted to the list. Have you thought about
converting them into a logwatch module (http://www.logwatch.org)?
Jason
-Original Message-
From: Glenn Nielsen [mailto:glenn;mail.more.net]
Sent: Wed 10/30/2002 3:56 AM
To: Tomcat Developers List
Hi,
Every now and then a message along those lines comes up. I've seen it
in all the open sources projects I've contributed to, and (what does
that say? I have too much free time? ;)) these are many.
I will quote a response, not written by me, that I think is a perfect
way to look at 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=14091.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
No. The scripts are written and they work. :-)
Jason Corley wrote:
I'd like to see this, even if it's just posted to the list. Have you thought about converting them into a logwatch module (http://www.logwatch.org)?
Jason
-Original Message-
From: Glenn Nielsen
Martin Algesten wrote:
Hi all,
Just some thoughts.
I've been using the 3.3.1 release for quite some time in a
mod_jk/apache/linux kind of setup and all was fine. Though a couple of
weeks ago I felt a need to start looking at new versions of all my
API's/products in order to make sure I stay on
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=13040.
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=14080.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Martin Algesten wrote:
Hi all,
Just some thoughts.
I've been using the 3.3.1 release for quite some time in a
mod_jk/apache/linux kind of setup and all was fine. Though a couple of
weeks ago I felt a need to start looking at new versions of all my
API's/products in order to make sure I stay on
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=12196.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
luehe 2002/10/30 09:41:23
Modified:jasper2/src/share/org/apache/jasper/compiler Collector.java
Generator.java Node.java Parser.java
ScriptingVariabler.java TagFileProcessor.java
TagLibraryInfoImpl.java
Glenn Nielsen wrote:
One note: mod_jk 1.2 JkRequestLogFormat for Apache 1.3 can log every
request that gets forwarded to Tomcat. Even if an HTTP request for a
single page results in multiple requests to Tomcat due to SSI.
I have found the reqeust data in the mod_jk logs to come in very
Pier Fumagalli wrote:
Thanks for listening... Hoping that Remy doesn't consider the ASF intent
to mirror all Jakarta nosise for notihg, right Remy?
However I do consider this phrase as noise.
Costin
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For
luehe 2002/10/30 10:06:09
Modified:jasper2/src/share/org/apache/jasper/compiler
ImplicitTagLibraryInfo.java
Log:
Pass null instead of tagdir to TagLibraryInfo constructor.
Revision ChangesPath
1.14 +4 -4
luehe 2002/10/30 10:20:21
Modified:jasper2/src/share/org/apache/jasper/compiler
JspDocumentParser.java PageDataImpl.java
TagConstants.java
Log:
Added urn:jsptagdir:path to XML view of JSP pages in JSP syntax
Revision Changes
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=14097.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Remy Maucherat wrote:
Martin Algesten wrote:
10373: I'm not convinced by the validity of the report.
13040: The spec is IMO not implementable, and most of the patches
submitted were wrong. Hence, the issue is not fixed. Sorry.
13846: This is a minor bug (IMHO) which will need a rather
Hmm... perhaps not drop it after all. I had a think about it and I still
would argue that the amount of developers or the speed of turning out
fixes is not the issue. As I said before, we are all doing this more or
less for fun.
Taking on board that its all about expectations and that you need
On 30/10/02 6:06 pm, Martin Algesten [EMAIL PROTECTED] wrote:
An incorrect If-Modified-Since response seems to shag mod_proxy. Now I
don't know how widely used mod_proxy is, or if perhaps this should be
fixed there instead. However I am concerned about this and as I pointed
out I am happy to
~~apologize in advance for the newbie question~~
I am running TC 4.1 on WIN2K.
I have configured the box to run TC as a service.
I am wanting to run JIKES as the JSP compiler so I have changed out the
parameters in the config files and followed the directions in the
documentation. I still
luehe 2002/10/30 12:53:11
Modified:jasper2/src/share/org/apache/jasper/compiler
TagFileProcessor.java
jasper2/src/share/org/apache/jasper/resources
messages.properties messages_es.properties
I am wanting to run JIKES as the JSP compiler so I have changed out the
parameters in the config files and followed the directions in the
documentation. I still have a sneaking suspicion that JIKES is not
compiling my JSP files. I believe that I should be seeing the jikes.exe
appear as a
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=12171.
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=13723.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
costin 2002/10/30 13:17:34
Modified:jk/native/common jk_ajp_common.c jk_lb_worker.c
Log:
Change some of the important messages to a more readable format.
Revision ChangesPath
1.31 +17 -17jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
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=12171.
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=13536.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
costin 2002/10/30 14:12:20
Modified:jk/native/common jk_ajp_common.c jk_connect.c
Log:
More trimming for error messages.
Now only one line ( and hopefully more informative ) is displayed if
we can't send the request to tomcat.
Revision ChangesPath
1.32 +11
On 30/10/02 20:02, Martin Algesten [EMAIL PROTECTED] wrote:
In a nutshell mod_proxy updates its cached entries with whatever new
headers are given to it. E.g. first request comes into mod_proxy and it
can't find the requested resource in its cache. It forwards on to my
tomcat who responds
costin 2002/10/30 14:21:06
Modified:jk/java/org/apache/jk/common ChannelSocket.java
Log:
Another log 'cleanup'.
This happens quite frequently and is very natural - many
apache servers are configured to restart themslef after a number
of errors.
Downgraded it to info
costin 2002/10/30 14:22:46
Modified:jk/java/org/apache/jk/common JkMX.java
Log:
Added support for starting the mx4j RMI connector. This is
obviously disabled by default.
Revision ChangesPath
1.7 +33 -0
I'm dropping my argument about labelling now. It will probably not lead
anywhere anyway.
Martin
Remy Maucherat wrote:
Martin Algesten wrote:
Hi all,
Just some thoughts.
I've been using the 3.3.1 release for quite some time in a
mod_jk/apache/linux kind of setup and all was fine. Though a
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=10891.
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=10891.
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=12699.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I've posted this on tomcat-user, but I can't seem to find the answer...
My setup:
Tomcat 4.1.12, Linux 2.4.9, IBM JRE 1.3.1, running Standalone SSL Coyote
conntector.
My problem is, I've tried to stress test my application and with
moderate load (20 concurrent connections) for a short time
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=14007.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
costin 2002/10/30 16:54:58
Modified:jk/java/org/apache/jk/common ChannelSocket.java
Log:
Added maxThreads property.
I think we should add more support for JMX on threads and the thread
pool - and then possibly do the conf on the TP
Revision ChangesPath
1.25
costin 2002/10/30 16:56:36
Modified:jk/java/org/apache/jk/server JkMain.java
Log:
Added support for coyote properties and 'shortcuts'.
This should solve a number of problems where information
was not passed from server.xml to jk.
Long term we should just consolidate all
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=12686.
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=14007.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Thanks, Costin. I'll pull this down and see if it works for the problem
I was seeing. I have this vain imagination that I'm actually going to
get some time to try tackling the bigger problem (single-sourced config
on all of this), but with the way things are going at work, it probably
won't
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=14110.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
It can't be correct to reset the error code to 200 when say a 404 have
happened.
A) Web caches, search engines etc will get confused by this. If a page
get spidered by say Google and the returned response code is a 404, then
the page will not be part of the index, which is correct, the
luehe 2002/10/30 18:11:40
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
Stop using the RuntimeException constructor that takes a String and an
exception object, as it is not available on J2SE 1.3 (notice that the JDK
requirement for JSP 2.0 was
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=14113.
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=14114.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello again,
The quote helps pointing out one important thing It's all a matter of
expectations. That's just another way of twisting my point, what we're
dealing with here is expectation management.
Apache Tomcat has reached a state where it is deployed widely around the
world in live
The reports I referred to were just the ones affecting me in my setup,
and my point was not about their validity, rather just an overall
feeling from using this particular software.
I have not tested other containers for spec compatibility, I can't claim
to have even tested this one.
I have a
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=14114.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
billbarker2002/10/30 22:24:59
Modified:src/share/org/apache/tomcat/modules/session SessionId.java
Log:
Disable session sharing when switching from HTTPS to HTTP.
There is a new secureCookie attribute that can be set to false to continue to
use the old behavior where session
We've agreed that the spec needs clarifying here. Unfortunatelly we can
not wait around for that since the current API is completely broken. A
ServletContext.getContext from the ROOT context currently ALWAYS returns
the ROOT context, no matter what. It is therefore impossible to
billbarker2002/10/30 22:41:38
Modified:.RELEASE-NOTES-3.3.2.txt
Log:
Document new session behavior.
Revision ChangesPath
1.14 +6 -1 jakarta-tomcat/RELEASE-NOTES-3.3.2.txt
Index: RELEASE-NOTES-3.3.2.txt
I'm pretty busy just at the moment, so I'm forwarding this to the list. I
does a pretty good job of addressing a lot of the newbie questions that come
up over and over on tomcat-user.
- Original Message -
From: Robert L Sowders [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday,
In a nutshell mod_proxy updates its cached entries with whatever new
headers are given to it. E.g. first request comes into mod_proxy and it
can't find the requested resource in its cache. It forwards on to my
tomcat who responds with something like:
HTTP/1.1 200
Content-Type: image/gif
Hello,
has anybody tested the largefile option with Tomcat 4.1.12?
In my opinion it seems to be without effect. No .dat file are
generated like in 4.0.x. I have also scanned the jasper code
for this option. The option is set at the EmbededServletOptions
class, but nobody seems to use this value
73 matches
Mail list logo
