Remy Maucherat wrote:
Hi,
Tomcat 5.0.17 Alpha is now available for testing.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.17-alpha/
Why the sources are under jakarta-tomcat-5.0.17-src/src and not under
jakarta-tomcat-5.0.17-src directly?
Rémy
Filip Hanik wrote:
Ok, I think I nailed it.
There is a memory leak in Tomcat 5. I downloaded a trial of JProbe (they
should provide free licenses for open source! :)
There is a class called o.a.coyote.RequestGroupInfo.java, in that class
there is a method called addRequestProcessor.
This method
Bill Barker wrote:
I'd be in favor of just dropping RequestInfo and RequestGroupInfo altogether
(and provide RequestListener commented out in web.xml that does the same
thing). Then people that want this can still get Request stats via JMX
(which I might use on a development site, but never on a
Remy Maucherat wrote:
Hi,
Tomcat 5.0.17 Alpha is now available for testing.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.17-alpha/
Where is the build.xml comming from?
I would like to fix things like:
available property=source.exists file=${basedir}/${tomcat.project} /
type=dir is missing.
jean-frederic clere wrote:
Remy Maucherat wrote:
Hi,
Tomcat 5.0.17 Alpha is now available for testing.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.17-alpha/
Why the sources are under jakarta-tomcat-5.0.17-src/src and not under
jakarta-tomcat-5.0.17-src directly?
Only in the .tar.gz, and
jean-frederic clere wrote:
Remy Maucherat wrote:
Hi,
Tomcat 5.0.17 Alpha is now available for testing.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.17-alpha/
Where is the build.xml comming from?
I would like to fix things like:
available property=source.exists
remm2004/01/15 01:38:49
Modified:.build.xml
Log:
- Make .tgz source package the same as the zip package. This wasn't Ant's
fault after all.
Revision ChangesPath
1.173 +2 -3 jakarta-tomcat-5/build.xml
Index: build.xml
jfclere 2004/01/15 01:50:57
Modified:resources build.xml
Log:
without typedir ant always tries to checkout the sources from repos.
Revision ChangesPath
1.4 +3 -2 jakarta-tomcat-5/resources/build.xml
Index: build.xml
Remy Maucherat wrote:
jean-frederic clere wrote:
Remy Maucherat wrote:
Hi,
Tomcat 5.0.17 Alpha is now available for testing.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.17-alpha/
Where is the build.xml comming from?
I would like to fix things like:
available property=source.exists
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=26162.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/15 04:53:24
Modified:jsr152/examples/WEB-INF web.xml
Log:
- Bug 26147: Fix typo in schemaLocation.
Revision ChangesPath
1.11 +1 -1 jakarta-servletapi-5/jsr152/examples/WEB-INF/web.xml
Index: web.xml
remm2004/01/15 04:54:54
Modified:catalina/src/conf server-minimal.xml
Log:
- Bug 26162: Fix typo.
Revision ChangesPath
1.3 +1 -1 jakarta-tomcat-catalina/catalina/src/conf/server-minimal.xml
Index: server-minimal.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=26162.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/15 05:16:41
Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java
Log:
- Properly remove the RequestInfo from the request group on thread end.
Revision ChangesPath
1.46 +4 -0
remm2004/01/15 05:16:49
Modified:coyote/src/java/org/apache/coyote RequestGroupInfo.java
RequestInfo.java
Log:
- Properly remove the RequestInfo from the request group on thread end.
Revision ChangesPath
1.2 +4 -0
Remy Maucherat wrote:
-1. There is no memory leak with this.
ByteChunks/CharChunks are always reused. If new ones are created, they
will be reused.
Arg, I have to find something.
I know ! It's all Costin's fault !
I didn't think about the scaling back feature of the thread pool, to
be honest. It
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=26147.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Howdy,
+1 one having a RequestListener -- I've been looking for a non-trivial example to
write and ship along with tomcat!
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 11:07 PM
To: Tomcat
I am trying to build mod_jk-1.2.5 from source on FreeBSD 4.9-RELEASE and I
encounter at the end of the build process the following error:
...
/usr/local/bin/bash /usr/local/apache/build/libtool --silent
--mode=install cp `pwd`/mod_jk.so
libtool: install: you must specify a destination
Try
Shapira, Yoav wrote:
Howdy, +1 one having a RequestListener -- I've been looking for a
non-trivial example to write and ship along with tomcat!
-0. This kind of stuff is already in the servlet API to some extent, and
all these event notifications will likely introduce overhead. This looks
like a
I'll tag a new release today. This is sooo boring !!
(why do people always find issues 5 minutes after I finish
uploading/signing a release ?)
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Gentlemen
Is there a reason for tomcat use of makefiles?
I have used Ant successfully for a number of engagements with spectacular
results.
The difference is like driving a yugo and a Ferrari..once you increase the
amount of functionaility of your environment by 100 you will not go back
Ant has
jfclere 2004/01/15 06:37:38
Modified:.build.properties.default build.xml
Log:
Add jaxen/saxpath location.
Revision ChangesPath
1.117 +3 -1 jakarta-tomcat-5/build.properties.default
Index: build.properties.default
Hi,
A user just noted that the jaas.jar that was present in server/lib for
tomcat 4.1.x is missing in tomcat 5. Is this by design? If so, I'll
add a note to the release notes. Or is this a simple mistake?
Yoav Shapira
Millennium ChemInformatics
This e-mail, including any attachments, is
David Meier wrote:
I am trying to build mod_jk-1.2.5 from source on FreeBSD 4.9-RELEASE and I
encounter at the end of the build process the following error:
...
/usr/local/bin/bash /usr/local/apache/build/libtool --silent
--mode=install cp `pwd`/mod_jk.so
libtool: install: you must specify a
--- Additional Comments From [EMAIL PROTECTED] 2004-01-14 13:03
There is a standard for encoding URIs
(http://www.w3.org/International/O-URL-
code.html) but this standard is not consistently followed by clients.
This causes a number of problems.
...
2. The Coyote HTTP/1.1 connector has a
remm2004/01/15 07:32:05
Modified:webapps/docs changelog.xml
Log:
- Update changelog.
Revision ChangesPath
1.33 +75 -0 jakarta-tomcat-catalina/webapps/docs/changelog.xml
Index: changelog.xml
Hi ppl,
Anyone here knows any resource about Tomcat and PHP performance comparinson
under linux?
Anyone knows wich one is faster?
Thanks in advance!
Thiago Souza
on Mon, 12 Jan 2004 17:04:07 +0100
Remy Maucherat [EMAIL PROTECTED] wrote:
Fixes were added a few days ago to the admin webapp to support dynamic
host creation. This is a first step. It should then be possible to add a
manager to a newly created host using the admin webapp (and then you're
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=26171.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
yoavs 2004/01/15 08:18:11
Modified:catalina/src/share/org/apache/catalina/valves
AccessLogValve.java
Log:
Added null check for current date for safety, after user reported
null date following webapp reload.
Revision ChangesPath
1.8 +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=26171.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
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=26171.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I am trying to implement my own JAAS LoginModule.
I configure server.xml
Realm className=org.apache.catalina.realm.JAASRealm
debug=99
appName=NadejJAAS
userClassName=com.micropole.jaas.memory.UserPrincipal
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=26147.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/15 09:18:31
Modified:jsr152/examples/WEB-INF web.xml
Log:
- Fix again schema location.
Revision ChangesPath
1.12 +1 -1 jakarta-servletapi-5/jsr152/examples/WEB-INF/web.xml
Index: web.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=26147.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/15 09:22:40
Modified:webapps/docs changelog.xml
Log:
- Update changelog.
Revision ChangesPath
1.34 +3 -12 jakarta-tomcat-catalina/webapps/docs/changelog.xml
Index: changelog.xml
-1. Please reconsider.
There is no memory leak, please check for yourself.
Rémy
dude, I spent hours on this yesterday with a profiler...how about giving in
a little bit :)
the leak is pretty bad, I ran up to 512MB in hours of heavy load.
Filip
-Original Message-
From: Remy Maucherat
Filip Hanik wrote:
dude, I spent hours on this yesterday with a profiler...how about giving in
a little bit :)
the leak is pretty bad, I ran up to 512MB in hours of heavy load.
For one, I couldn't reproduce the problem. I had to use my imagination
and saw that there was an issue when the thread
I dont think setting maxSpareThreads==maxThreads is a good solution to a
problem as this memory leak. I still have to verify that that would actually
solve the problem
if we don't want to remove request info, lets fix it.
Filip
-Original Message-
From: Remy Maucherat [mailto:[EMAIL
This sort of memory leak can't be left unaddressed -- i.e. you shouldn't
have to change the settings to avoid an intolerable memory leak.
Is this issue new to 5.0.17 or was it in 5.0.16 as well? In either
case, it would be good to see this fixed in 5.0.17 -- but it is all the
more critical if
I ran HTTP client on windows, Tomcat on RH8 AND RH9, both of them have the
leak.
I ran tomcat through both OptimizeIt and JProbe yesterday, and both of them
showed the leak.
it should be very easy to reproduce, you just have to be patient...it takes
time for the memory to grow, but it does and
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=26174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Filip Hanik wrote:
I ran HTTP client on windows, Tomcat on RH8 AND RH9, both of them have the
leak.
I ran tomcat through both OptimizeIt and JProbe yesterday, and both of them
showed the leak.
it should be very easy to reproduce, you just have to be patient...it takes
time for the memory to grow,
5.0.17 seemed to work fine overall [though I'm anxiously awaiting the
memory leak resolution] -- including the new useBodyEncodingForURI flag :-)
I did notice that out of 992 JSP pages Tomcat 5.0.16 has successfully
compiled (via an Ant precompilation using Tomcat's jspc) only 899 were
Howdy,
I did notice that out of 992 JSP pages Tomcat 5.0.16 has successfully
compiled (via an Ant precompilation using Tomcat's jspc) only 899 were
successfully compiled by 5.0.17. I looked into this further and
discovered that 5.0.16 misreported 3 failures as successes as the jspc
task failed
Shapira, Yoav wrote:
Howdy,
I did notice that out of 992 JSP pages Tomcat 5.0.16 has successfully
compiled (via an Ant precompilation using Tomcat's jspc) only 899 were
successfully compiled by 5.0.17. I looked into this further and
discovered that 5.0.16 misreported 3 failures as successes
Yap! That was it. I am fairly new to FreeBSD and I was not aware about
that issue. Thanx a lot!
Dave
David Meier wrote:
I am trying to build mod_jk-1.2.5 from source on FreeBSD 4.9-RELEASE and I
encounter at the end of the build process the following error:
...
/usr/local/bin/bash
I'll try the fix since I am still on the eval period of the profilers :)
thanks
Filip
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 9:56 AM
Subject: Re: Found it - WAS: Memory leak
Filip Hanik
Filip Hanik wrote:
I'll try the fix since I am still on the eval period of the profilers :)
Cool :) (crossing all fingers)
You know there's also that tomcat-committers mailing list for the issues
that make people nervous (security, etc) ;)
Rémy
From: Remy Maucherat [EMAIL PROTECTED]
Filip Hanik wrote:
I'll try the fix since I am still on the eval period of the profilers :)
Cool :) (crossing all fingers)
You know there's also that tomcat-committers mailing list for the issues
that make people nervous (security, etc) ;)
no, I
Hi,
A new new build is now available for testing: Tomcat 5.0.18 Alpha.
http://www.apache.org/dist/jakarta/tomcat-5/v5.0.18-alpha/
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 5:24 AM
Subject: Re: Found it - WAS: Memory leak
Remy Maucherat wrote:
-1. There is no memory leak with this.
ByteChunks/CharChunks are always
Bill Barker wrote:
Remy Maucherat wrote:
-1. There is no memory leak with this.
ByteChunks/CharChunks are always reused. If new ones are created, they
will be reused.
Arg, I have to find something.
I know ! It's all Costin's fault !
I didn't think about the scaling back feature of the thread
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 11:41 AM
Subject: Re: Found it - WAS: Memory leak
Bill Barker wrote:
Remy Maucherat wrote:
-1. There is no memory leak with this.
Bill Barker wrote:
I'm almost certain JK doesn't register the RequestInfo objects. It
should (and it's a bug), but actually it doesn't. I tried to have the
status servlet work with JK also, and had partial fixes, but in the end,
I didn't find the feature too worthwhile (and my fixes were hacks),
setting maxSpareThreads==minSpareThreads==maxThreads
does take care of the memory leak with the new code,
however, going with the default server.xml settings, tomcat is still leaking
memory. I will delve into this when I get home tonight, that is when I have
access to the profiler.
have a good
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 12:33 PM
Subject: Re: Found it - WAS: Memory leak
Bill Barker wrote:
I'm almost certain JK doesn't register the RequestInfo objects. It
should
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=25965.
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=25965.
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=25965.
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=26181.
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=26181.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
billbarker2004/01/15 19:14:11
Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java
Log:
Fix JMX self-registration when loading the normal way.
Revision ChangesPath
1.48 +8 -8
jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java
billbarker2004/01/15 19:57:59
Modified:jk/java/org/apache/jk/common HandlerRequest.java
Log:
Add an option to allow the admin to *not* JMX register the requests.
This is mostly because it may take awhile to plug the memory leaks that registering
the requests causes (esp. for
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=26183.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Mon, Jan 12, 2004 at 11:43:44AM -0700, George Sexton wrote:
Here is my thinking. Of course, I am a lowly user and not a developer
but I think it pretty much covers the issues. The major issues from my
perspective are:
1)Admin cannot deploy privileged applications. This requires
billbarker2004/01/15 22:48:21
Modified:jk/java/org/apache/jk/common ChannelSocket.java
HandlerRequest.java
jk/java/org/apache/jk/core JkHandler.java
Log:
Initial fix for memory leak with registering Requests.
This only currently fixes
69 matches
Mail list logo
