RE: [4.1.6] New milestone release soon
Ok, I tried and I can't reproduce it. Costin, The problem has been fixed and works fine in 4.1.7. I couldn't get the thing to compile from CVS, so I had to wait for the 4.1.7 milestone. Thanks for your help. Dave. I used an app doing big posts/gets - it all works fine for me. If you can provide code to reproduce it ( like a servlet and an java client ) - it would be great. All I can figure from the log: [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 7 (-1) out of 7 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Ok, I tried and I can't reproduce it. I used an app doing big posts/gets - it all works fine for me. If you can provide code to reproduce it ( like a servlet and an java client ) - it would be great. All I can figure from the log: [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 7 (-1) out of 7 That basically means ap_rwrite() returned -1, when attempting to send 7 bytes. That may mean the browser closed the connection - possibly because of a mismatch between the content length and what was sent. It seems you use an older version of mod_jk - the line numbers on ajp_common.c doesn't match. If you can try again with the latest, I can do more guessing. But without a reproduction I can't help more. One problem is in the fragmentation of the output - I'll investigate this a bit more. It seems we're sending 8k buffers, and that gets fragmented in 2 packets because the ajp buffer is 8k and 7 bytes are used for the header. But that shouldn't create a problem. ( we just need to find a way for jk2 to change the buffer size without braking the backward compat !) Costin [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (935)]: Error ajp_process_callback - write failed [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (1349)]: Into jk_endpoint_t::done, closing connection 0 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (536)]: In jk_endpoint_t::ajp_close_endpoint [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (543)]: In jk_endpoint_t::ajp_close_endpoint, closed sd = 19 Any ideas? Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 02 July 2002 17:49 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon Got it. I'll check in, please test again. Costin On Tue, 2 Jul 2002, David Oxley wrote: Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev
RE: [4.1.6] New milestone release soon
Costin, As CVS seems to be down. I cannot get the new jakarta-tomcat-connectors. Did you only change jakarta-tomcat-connectors/jk/java/org/apache/jk/common/MsgAjp.java to fix this bug. Because I just tried a new tomcat-jk2.jar with the new MsgAjp.java and it still fails. It does get further. Here is my new mod_jk.log: [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #142 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (462)]: ajp_unmarshal_response: status = 200 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (467)]: ajp_unmarshal_response: Number of headers is = 4 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[0] [ETag] = [W/18404-1025287018000] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[1] [Last-Modified] = [Fri, 28 Jun 2002 17:56:58 GMT] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[2] [Content-Type] = [image/jpeg] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[3] [Content-Length] = [18404] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #4 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4096 (4096) out of 8185 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4089 (4089) out of 4089 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 7 (7) out of 7 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #4 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4096 (4096) out of 8185 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 4089 (4089) out of 4089 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 7 (-1) out of 7 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (935)]: Error ajp_process_callback - write failed [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (1349)]: Into jk_endpoint_t::done, closing connection 0 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (536)]: In jk_endpoint_t::ajp_close_endpoint [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (543)]: In jk_endpoint_t::ajp_close_endpoint, closed sd = 19 Any ideas? Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 02 July 2002 17:49 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon Got it. I'll check in, please test again. Costin On Tue, 2 Jul 2002, David Oxley wrote: Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy
RE: [4.1.6] New milestone release soon
Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Got it. I'll check in, please test again. Costin On Tue, 2 Jul 2002, David Oxley wrote: Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- 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: [4.1.6] New milestone release soon
Costin, This problem still happens with 4.1.6. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- 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: [4.1.6] New milestone release soon
I think we were each tracking down a different memory leak. The one I found is in DBCP, I should have that patched sometime tomorrow. Oh, ok. I'll wait a bit for your commit (and I'll apply the Tyrex 1.0 bug I fixed). It is definitely not as critical that the memory leak I fixed (using the RD was leaking memory, although it really looks like a JDK bug instead of a TC bug). Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
I haven't had a chance to work out how to compile from CVS yet. To save me time, is there anywhere I can download a recent 4.1.6-dev build so I can quickly test it before it is tagged? Thanks. Dave. -Original Message- From: Dave [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 20:04 To: [EMAIL PROTECTED] Subject: RE: [4.1.6] New milestone release soon Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin I'm using 4.1.5. I will try a nightly tonight. Thanks. Dave. -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. Since the last two issues are resolved, I plan to tag the new 4.1.6 milestone later today. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
I just noticed a memory leak in a build from CVS in the last 24 hours. I am working on tracking it down. I have seen that kind of report on tomcat-user, but people have been unable to help reproduce it. They've tried with Coyote HTTP/1.1 + TC 4.0.x (no leak), as well as Jasper 2 + TC 4.0.x (no leak). It's very odd there's a memory leak in the Catalina core. I tried reproducing it using servlet and JSP based tests, but without any success. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
hey remy, I'll send you more information in a hour with more details. I haven't been able to find time to run the JProbe thread analyzer tests, but I can atleast send you the test JSTL pages and JMeter settings I am using to reproduce it. If that is cool with you, I'll get the files together and send it to you. peter Remy Maucherat wrote: I just noticed a memory leak in a build from CVS in the last 24 hours. I am working on tracking it down. I have seen that kind of report on tomcat-user, but people have been unable to help reproduce it. They've tried with Coyote HTTP/1.1 + TC 4.0.x (no leak), as well as Jasper 2 + TC 4.0.x (no leak). It's very odd there's a memory leak in the Catalina core. I tried reproducing it using servlet and JSP based tests, but without any success. 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: [4.1.6] New milestone release soon
hey remy, I'll send you more information in a hour with more details. I haven't been able to find time to run the JProbe thread analyzer tests, but I can atleast send you the test JSTL pages and JMeter settings I am using to reproduce it. If that is cool with you, I'll get the files together and send it to you. This is not very useful since you said the problem isn't with Jasper (JSTL is probably the least specific test you can come up with, more or less). If the problem really isn't with Jasper, I should be able to reproduce it with servlets and/or other JSPs, and I'm not. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
I haven't ruled out JSTL as a cause since my test show it is memory intensive. I doubt it is JSTL alone, but it could be a combination. I've produced the bug with jdk1.3.1 on both windows and solaris. I sent you additional information and the exception I am getting. It's probably not going to be any help, but maybe it will rule out possible causes. peter Remy Maucherat wrote: hey remy, I'll send you more information in a hour with more details. I haven't been able to find time to run the JProbe thread analyzer tests, but I can atleast send you the test JSTL pages and JMeter settings I am using to reproduce it. If that is cool with you, I'll get the files together and send it to you. This is not very useful since you said the problem isn't with Jasper (JSTL is probably the least specific test you can come up with, more or less). If the problem really isn't with Jasper, I should be able to reproduce it with servlets and/or other JSPs, and I'm not. 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: [4.1.6] New milestone release soon
I haven't ruled out JSTL as a cause since my test show it is memory intensive. I doubt it is JSTL alone, but it could be a combination. I've produced the bug with jdk1.3.1 on both windows and solaris. I sent you additional information and the exception I am getting. It's probably not going to be any help, but maybe it will rule out possible causes. I can hammer the Transform example of JSTL with ab (concurrency 40) without any memory problems (JDK 1.3 / Win2k). Other that there's one session created per request, and that slowly eats up memory. Your example uses another taglib. I'm going to try to download it, but I really doubt there's a problem now. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
Here is a bit more information on why I haven't ruled out JSTL or 1.2 JSP tags as a possible cause. 1. the standard examples all run fine and do not exhibit a memory leak, including the simpletag example. 2. the other person experiencing memory leak is also using JSP tags extensively. 3. my JSTL pages produce the memory leak every time. 4. static files and images do not produce the bug. One difference I can think of is JSTL accesses the pageContext frequently. My test pages use JSTL c:import quite a bit, which might be causing the leak? In either case, I sent my test pages to Remy. peter Remy Maucherat wrote: hey remy, I'll send you more information in a hour with more details. I haven't been able to find time to run the JProbe thread analyzer tests, but I can atleast send you the test JSTL pages and JMeter settings I am using to reproduce it. If that is cool with you, I'll get the files together and send it to you. This is not very useful since you said the problem isn't with Jasper (JSTL is probably the least specific test you can come up with, more or less). If the problem really isn't with Jasper, I should be able to reproduce it with servlets and/or other JSPs, and I'm not. 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: [4.1.6] New milestone release soon
Here is a bit more information on why I haven't ruled out JSTL or 1.2 JSP tags as a possible cause. 1. the standard examples all run fine and do not exhibit a memory leak, including the simpletag example. 2. the other person experiencing memory leak is also using JSP tags extensively. 3. my JSTL pages produce the memory leak every time. 4. static files and images do not produce the bug. One difference I can think of is JSTL accesses the pageContext frequently. My test pages use JSTL c:import quite a bit, which might be causing the leak? In either case, I sent my test pages to Remy. After getting the 'string', I can get the memory problem with the given example. After looking into it, it happens also with the include and forward examples, so it's either a bug in the page context, or more likely with 4.1's request dispatcher (since Jasper 2 + 4.0.x supposedly works well). Given that Coyote + 4.0.x reportedly works fine, it is also unlikely there's a problem there. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
Glenn Nielsen wrote: I have been able to reproduce the memory leak with the following config: Apache 1.3.26/mod_jk1.2/Ajp13/Tomcat4.1 and Jasper1 built from CVS HEAD. A JSP page which uses the dbtags taglib, a JNDI named JDBC DataSource, and the DBCP as the datasource exhibits the problem. I am currently doing memory profiling using OptimizeIt to see if I can find it. I have fixed the memory leak (and optimized the request dispatcher a bit in the process). I fail to understand why the memory was leaked, as I couldn't find any references kept anywhere (maybe it was a GC bug ?). Please confirm it is fixed if you can. The VM crash also went away after updating my CVS. So everything looks good, and I'll tag 4.1.6 tomorrow. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
hey remy, I am running JProbe now. finally I have time to run the test. If I find anything I'll post it. peter --- Remy Maucherat [EMAIL PROTECTED] wrote: Glenn Nielsen wrote: I have been able to reproduce the memory leak with the following config: Apache 1.3.26/mod_jk1.2/Ajp13/Tomcat4.1 and Jasper1 built from CVS HEAD. A JSP page which uses the dbtags taglib, a JNDI named JDBC DataSource, and the DBCP as the datasource exhibits the problem. I am currently doing memory profiling using OptimizeIt to see if I can find it. I have fixed the memory leak (and optimized the request dispatcher a bit in the process). I fail to understand why the memory was leaked, as I couldn't find any references kept anywhere (maybe it was a GC bug ?). Please confirm it is fixed if you can. The VM crash also went away after updating my CVS. So everything looks good, and I'll tag 4.1.6 tomorrow. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
after 3 hours of trying to get JProbe to run correctly I give up. It's 12am and I'm too tired. If anyone knows how to get tomcat 4.1.5, jasper2 and JProbe profiler to work correctly I'll try to run the tests. since jasper2 uses ANT and I don't see how to pass Java_home from jprobe to the shell it won't compile pages. peter --- Remy Maucherat [EMAIL PROTECTED] wrote: Glenn Nielsen wrote: I have been able to reproduce the memory leak with the following config: Apache 1.3.26/mod_jk1.2/Ajp13/Tomcat4.1 and Jasper1 built from CVS HEAD. A JSP page which uses the dbtags taglib, a JNDI named JDBC DataSource, and the DBCP as the datasource exhibits the problem. I am currently doing memory profiling using OptimizeIt to see if I can find it. I have fixed the memory leak (and optimized the request dispatcher a bit in the process). I fail to understand why the memory was leaked, as I couldn't find any references kept anywhere (maybe it was a GC bug ?). Please confirm it is fixed if you can. The VM crash also went away after updating my CVS. So everything looks good, and I'll tag 4.1.6 tomorrow. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.6] New milestone release soon
On Wed, 26 Jun 2002, Remy Maucherat wrote: There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. I'll verify again ( I'm curently using 4.1.2 snapshot of jasper2 ). I think the bug was pretty much a showstopper - we're talking about trivial and common uses of struts ( and I assume jstl or any tag libs that have iterations and conditions ). Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- 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: [4.1.6] New milestone release soon
Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin I'm using 4.1.5. I will try a nightly tonight. Thanks. Dave. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
