DO NOT REPLY [Bug 28612] New: - configure script fails locating libapr
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28612. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28612 configure script fails locating libapr Summary: configure script fails locating libapr Product: Tomcat 5 Version: 5.0.19 Platform: Macintosh OS/Version: MacOS X Status: NEW Severity: Blocker Priority: Other Component: Connector:Coyote AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Because the jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/configure script is looking for libapr as a .so library instead of .dylib for libapr, configure fails. Mac OS uses .dylib for dynamic libraries. See jakarta-tomcat-connectors- jk2-2.0.4-src/jk/native2/configure lines 18730-18738 and 18927-18935. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Movie
shachor wrote: I'm going to unsubscribe Gal from tomcat-dev for now, since a lot of spam is coming through this old email. Subscribe again if you'd like to be on the list (but with a slightly different email so we don't get the spam ;) ). (Apache really needs to add competent spam filtering ...) Thanks, Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Movie
-Original Message- From: Remy Maucherat I'm going to unsubscribe Gal from tomcat-dev for now, since a lot of spam is coming through this old email. Subscribe again if you'd like to be on the list (but with a slightly different email so we don't get the spam ;) ). (Apache really needs to add competent spam filtering ...) Yes, It seems that even my account is missused, I even send myself a virus yesterday. Not to speak that some [EMAIL PROTECTED] is constantly sending me a viruses :-). MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27534] - Servlet invoked twice with JK2 when response is not read completely.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27534. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27534 Servlet invoked twice with JK2 when response is not read completely. --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 08:27 --- I get the same behaviour by making calls directly to tomcat's listenning port (not through apache). In addition I get the servlet's output rendered twice by my browser. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Movie
Mladen Turk wrote: Yes, It seems that even my account is missused, I even send myself a virus yesterday. Not to speak that some [EMAIL PROTECTED] is constantly sending me a viruses :-). As long as it's private mail, it's a smaller issue (I obviously get hundreds of viruses a day). Of course, it's only a matter a time until this reaches mailing lists :( Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Movie
Remy Maucherat wrote: I'm going to unsubscribe Gal from tomcat-dev for now, since a lot of spam is coming through this old email. Subscribe again if you'd like to be on the list (but with a slightly different email so we don't get the spam ;) ). (Apache really needs to add competent spam filtering ...) Getting mail servers to start using something like SPF (http://spf.pobox.com/) would go a long ways to keeping all these forged emails with viruses from being spread around. Seems like large mailing lists would be a great candidate for running SPF checks on incoming email. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28616] New: - TOMCAT AND LOTUS NOTES 6 - AllocHandle: OUT OF PRIVATE HANDLES!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28616. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28616 TOMCAT AND LOTUS NOTES 6 - AllocHandle: OUT OF PRIVATE HANDLES! Summary: TOMCAT AND LOTUS NOTES 6 - AllocHandle: OUT OF PRIVATE HANDLES! Product: Tomcat 3 Version: 3.3.1 Release Candidate 1 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Webapps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a problem with tomcat and Lotus Notes 6 on the web by the request to notes when tomcat crash the response is: NotesException: Invalid user name/password on tomcat it gives to me this response,I try to restart Tomcat via web but it don't go. AllocHandle: OUT OF PRIVATE HANDLES! -- pid 0664 Handles used so far 6399, Maximum handles = 16443, error = 0x107 I gotta only stop and restart the server. Before it gives to me this error on notes by a NotesInitthread without NotesStopThread or something of similar.. but know with the command sometimes it gives that error... what i gotta do? tHANKS A LOT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw: Lesbian Mpeg
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw: `·.¸MPEG`·.¸
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Asses Mpeg's
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw: `·.¸MPEG`·.¸
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw:'''~~movie'''~~25
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:(movie)
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw: }Fucking{
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (movie)
Anyone could find a good explanation as to why unsubscribing the address didn't work ? (the list manager says [EMAIL PROTECTED] is not subscribed) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: (movie)
Can people not on the list send messages to the list? I believe they can unless the list is a moderated list... -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 10:59 AM To: Tomcat Developers List Subject: Re: (movie) Anyone could find a good explanation as to why unsubscribing the address didn't work ? (the list manager says [EMAIL PROTECTED] is not subscribed) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28039] - Cluster Support for SingleSignOn
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28039 Cluster Support for SingleSignOn [EMAIL PROTECTED] changed: What|Removed |Added Component|Catalina|Catalina:Cluster --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 15:15 --- I can add it to my todo list, this should be very simple to implement into Tomcat clustering as well. I'm not biased like Remy ;-) to put it into JBoss, he he he - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (movie)
what does the mail header say? or maybe some one else already unsubscribed the address :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote: Anyone could find a good explanation as to why unsubscribing the address didn't work ? (the list manager says [EMAIL PROTECTED] is not subscribed) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs
Ambiguity with respect to setParent() and tag files
Hello, I am trying to resolve an ambiguity with respect to javax.servlet.jsp.tagext.[Simple]Tag.setParent() and tag files. If I place a tag (simple or classic, doesn't matter) at the top-level within a tag file, should it have a parent? I had expected that its parent would be the SimpleTag that is the tag file itself, thus providing a parent chain into the calling JSP, but the Tomcat 5.0.19 implementation sets its parent to null. The JSP 2.0 specification and JavaDoc say only The setParent() method is only called if the element is nested within another tag invocation. I could interpret this to mean nested statically, in which case the current behavior is correct, or nested dynamically, in which case it is incorrect. It would be extremely useful if a tag within a tag file that expects, for example, a transaction context provided by an ancestor tag, could communicate with that ancestor tag even if the ancestor is in the JSP that invoked the tag file. Otherwise, I can't generally take a portion of my JSP and make it reusable by putting it into a tag file. In implementation, this interpretation would mean that a tag at the top level within a tag file should be initialized with setParent(this) (or setParent(new TagAdapter(this))) instead of setParent(null). I have sent an e-mail to the JSR-152 address to request a spec clarification. Any opinions here on the correct behavior? Thanks, Tony Deigh RepWire, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: (movie)
Hi, The address may have been unsubscribed (though I didn't do it, as I know it's a legit address and a legit subscriber), or the from address may have been spoofed. We see a ton of those and must look through the mail headers to spot a real address. To other poster: this is a moderated list and only subscribers may post. Yoav Shapira Millennium Research Informatics -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 11:17 AM To: Tomcat Developers List Subject: Re: (movie) what does the mail header say? or maybe some one else already unsubscribed the address :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote: Anyone could find a good explanation as to why unsubscribing the address didn't work ? (the list manager says [EMAIL PROTECTED] is not subscribed) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (movie)
On Tue, 27 Apr 2004, Remy Maucherat [EMAIL PROTECTED] wrote: (the list manager says [EMAIL PROTECTED] is not subscribed) Is it subscribed to the -allow list? http://www.ezmlm.org/ezman-0.32/ezman2.html#ss2.4 and related info on that page may help. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ambiguity with respect to setParent() and tag files
We have received several emails from your email address by a blind copy. We are the technology support help desk for the Cobb County School System. I am sure these emails are being sent to us in error. [EMAIL PROTECTED] 4/27/2004 11:21:19 AM Hello, I am trying to resolve an ambiguity with respect to javax.servlet.jsp.tagext.[Simple]Tag.setParent() and tag files. If I place a tag (simple or classic, doesn't matter) at the top-level within a tag file, should it have a parent? I had expected that its parent would be the SimpleTag that is the tag file itself, thus providing a parent chain into the calling JSP, but the Tomcat 5.0.19 implementation sets its parent to null. The JSP 2.0 specification and JavaDoc say only The setParent() method is only called if the element is nested within another tag invocation. I could interpret this to mean nested statically, in which case the current behavior is correct, or nested dynamically, in which case it is incorrect. It would be extremely useful if a tag within a tag file that expects, for example, a transaction context provided by an ancestor tag, could communicate with that ancestor tag even if the ancestor is in the JSP that invoked the tag file. Otherwise, I can't generally take a portion of my JSP and make it reusable by putting it into a tag file. In implementation, this interpretation would mean that a tag at the top level within a tag file should be initialized with setParent(this) (or setParent(new TagAdapter(this))) instead of setParent(null). I have sent an e-mail to the JSR-152 address to request a spec clarification. Any opinions here on the correct behavior? Thanks, Tony Deigh RepWire, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (movie)
Dear Sir, Thank you for your e-mail. Please inform us more detailed how we can assist you? Please let us know if any questions remain open. We will be happy to assist you. Sincerely, Bilge Havayir Your element 5 team __ element 5 - the e-way of software at http://www.element5.com * element 5 Germany - France - Italy - Sweden - UK - USA * __ Original Message Follows: - Anyone could find a good explanation as to why unsubscribing the address didn't work ? (the list manager says [EMAIL PROTECTED] is not subscribed) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw: }Fucking{
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fw:'''~~movie'''~~25
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XXX Funny movie
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:(movie)
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XXX Funny movie
Hi, I've put [EMAIL PROTECTED] on the deny list for tomcat-dev, so no more messages from that address should get through. I've also emailed [EMAIL PROTECTED] to let him know of this and ask him to contact us after cleaning up his computer. Yoav Shapira Millennium Research Informatics -Original Message- From: shachor [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 4:54 PM To: [EMAIL PROTECTED] Subject: XXX Funny movie This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wrong timeIdel value in StandardSession
The test needs to be updated to test for the correct behaviour now that the bug is fixed. :-) BTW, I did post a proposed patch which fixes this bug and improves performance of the JDBCStore. No one has replied. Regards, Glenn On Mon, Apr 26, 2004 at 10:37:08PM -0700, Amy Roh wrote: Bill Barker wrote: - Original Message - From: Amy Roh [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, April 26, 2004 6:07 PM Subject: wrong timeIdel value in StandardSession The following patch causes regression where sessions don't expire when it should. I have a test app that does refresh every 70 sec. When I set timeout to 2 minute - the session *never* expires. I see the change to be not so much a regression as a bug-fix :). Your app is accessing the session every 70 sec, so the session is never idle for the required 2 min to allow it to expire. I see on Remy's commit that Ths patch needs to be tested for possible regressions. The test jsp actually checks if the session expired after timeout and alerts when refreshed. I am attaching the jsp. cvs diff -r 1.26 -r 1.27 StandardSession.java 587c587 int timeIdle = (int) ((timeNow - lastAccessedTime) / 1000L); --- int timeIdle = (int) ((timeNow - thisAccessedTime) / 1000L); I have added some debugging statements and found the following. setMaxInactiveInterval 120 timeIdle now 0 timeIdle before 0 timeIdle now 36 timeIdle before 36 timeIdle now 116 timeIdle before 186 WOULD HAVE EXPIRED WITH OLD TIMEIDLE timeIdle now 70 timeIdle before 70 timeIdle now 0 timeIdle before 70 timeIdle now 26 timeIdle before 96 timeIdle now 70 timeIdle before 140 WOULD HAVE EXPIRED WITH OLD TIMEIDLE timeIdle now 0 timeIdle before 70 timeIdle now 16 timeIdle before 86 timeIdle now 70 timeIdle before 140 WOULD HAVE EXPIRED WITH OLD TIMEIDLE timeIdle now 0 timeIdle before 70 timeIdle now 6 timeIdle before 76 timeIdle now 66 timeIdle before 137 WOULD HAVE EXPIRED WITH OLD TIMEIDLE timeIdle now 70 timeIdle before 140 WOULD HAVE EXPIRED WITH OLD TIMEIDLE timeIdle now 0 timeIdle before 70 timeIdle now 56 timeIdle before 127 WOULD HAVE EXPIRED WITH OLD TIMEIDLE Let me know what you think Thanks, Amy I propose to revert the patch. I'm -1 on reverting unless you can explain why you think that the previous behavior is correct wrt the spec. And, no, the fact that this bug has been in every version of Tomcat back to at least 3.2.x isn't good enough ;-). Thanks, Amy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] New: - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals Summary: JAASRealm fix to permit user-specified user/group Principals Product: Tomcat 5 Version: 5.0.19 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This bug report was previously posted to tomcat-dev as [PATCH] JAASRealm fixes on 24-Apr-2004. These patches enable JAASRealm to work as advertised. In particular, JAASRealm can use user-specified Principal classes for both user Principals and group Principals, just like the documentation says it is supposed to be able to do. In addition, I have added support for digested passwords similar to the way the other Realm implementations work. I have patched three files: JAASRealm.java, JAASCallbackHandler.java, and LocalStrings.properties. I have unquestionably fouled up the @version Javadoc tags... one assumes the responsible parties (surely not me!) can fix these prior to committing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 16:17 --- Created an attachment (id=11354) JAASRealm.patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 16:17 --- Created an attachment (id=11355) JAASCallbackHandler.patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 16:18 --- Created an attachment (id=11356) LocalStrings.patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28632] New: - connection_util.jar missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28632. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28632 connection_util.jar missing Summary: connection_util.jar missing Product: Tomcat 3 Version: 3.3.2 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] connection_util.jar missing is missing in the jakarta-tomcat-3.3.2\lib\common directory in the Tomcat3.3.2 zip file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28612] - configure script fails locating libapr
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28612. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28612 configure script fails locating libapr [EMAIL PROTECTED] changed: What|Removed |Added Component|Connector:Coyote|Native:JK - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28286] - Loosely couple SingleSignOn Valve and Authenticators
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28286. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28286 Loosely couple SingleSignOn Valve and Authenticators [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28632] - connection_util.jar missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28632. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28632 connection_util.jar missing [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 17:37 --- Sorry, but there is no connection_util.jar in a Tomcat 3.3.x distribution. Rechecking a downloaded zip, the PGP signature is still good and I don't find any missing jars. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XXX Funny movie
Shapira, Yoav wrote: I've put [EMAIL PROTECTED] on the deny list for tomcat-dev, so no more messages from that address should get through. I've also emailed [EMAIL PROTECTED] to let him know of this and ask him to contact us after cleaning up his computer. It looks to me that the headers of the email are forged, so I doubt that [EMAIL PROTECTED] is the one actually sending the emails. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session DeltaManager.java DeltaSession.java
fhanik 2004/04/27 10:50:43
Modified:modules/cluster/src/share/org/apache/catalina/cluster/session
DeltaManager.java DeltaSession.java
Log:
Added in the ability to run the DeltaManager/DeltaSession without a container, so
that a different clustering plug in can be used to backup sessions in a
primary/secondary store
Revision ChangesPath
1.23 +12 -2
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaManager.java
Index: DeltaManager.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaManager.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- DeltaManager.java 8 Apr 2004 15:30:11 - 1.22
+++ DeltaManager.java 27 Apr 2004 17:50:43 - 1.23
@@ -369,8 +369,18 @@
ReplicationStream ois = null;
Loader loader = null;
ClassLoader classLoader = null;
+//fix to be able to run the DeltaManager
+//stand alone without a container.
+//use the Threads context class loader
+if ( container != null )
+loader = container.getLoader();
+if ( loader != null )
+classLoader = loader.getClassLoader();
+else
+classLoader = Thread.currentThread().getContextClassLoader();
+//end fix
fis = new ByteArrayInputStream(data);
-ois = new ReplicationStream(fis,container.getLoader().getClassLoader());
+ois = new ReplicationStream(fis,classLoader);
session.getDeltaRequest().readExternal(ois);
ois.close();
return session.getDeltaRequest();
1.22 +131 -112
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaSession.java
Index: DeltaSession.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaSession.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- DeltaSession.java 7 Apr 2004 19:02:31 - 1.21
+++ DeltaSession.java 27 Apr 2004 17:50:43 - 1.22
@@ -396,36 +396,42 @@
// Notify interested application event listeners
Context context = (Context) manager.getContainer();
-Object listeners[] = context.getApplicationLifecycleListeners();
-if (listeners != null) {
-HttpSessionEvent event =
-new HttpSessionEvent(getSession());
-for (int i = 0; i listeners.length; i++) {
-if (!(listeners[i] instanceof HttpSessionListener))
-continue;
-HttpSessionListener listener =
-(HttpSessionListener) listeners[i];
-try {
-fireContainerEvent(context,
- beforeSessionCreated,
- listener);
-listener.sessionCreated(event);
-fireContainerEvent(context,
- afterSessionCreated,
- listener);
-} catch (Throwable t) {
+//fix for standalone manager without container
+if ( context != null ) {
+Object listeners[] = context.getApplicationLifecycleListeners();
+if (listeners != null) {
+HttpSessionEvent event =
+new HttpSessionEvent(getSession());
+for (int i = 0; i listeners.length; i++) {
+if (! (listeners[i] instanceof HttpSessionListener))
+continue;
+HttpSessionListener listener =
+(HttpSessionListener) listeners[i];
try {
fireContainerEvent(context,
+ beforeSessionCreated,
+ listener);
+listener.sessionCreated(event);
+fireContainerEvent(context,
afterSessionCreated,
listener);
-} catch (Exception e) {
-;
+} catch (Throwable t) {
+try {
+fireContainerEvent(context,
+ afterSessionCreated,
+ listener);
+} catch (Exception e) {
+;
+
RE: XXX Funny movie
Hi, It looks to me that the headers of the email are forged, so I doubt that [EMAIL PROTECTED] is the one actually sending the emails. You're most likely right, but I looked through the headers, couldn't find anything else, and so went ahead. It seems OK so far. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XXX Funny movie
Shapira, Yoav wrote: It looks to me that the headers of the email are forged, so I doubt that [EMAIL PROTECTED] is the one actually sending the emails. You're most likely right, but I looked through the headers, couldn't find anything else, and so went ahead. It seems OK so far. Yeah, at least it got the SPAM to stop coming through. :-) -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspC.java
luehe 2004/04/27 11:04:37
Modified:jasper2/src/share/org/apache/jasper JspC.java
Log:
Fixed indentation
Revision ChangesPath
1.71 +5 -6
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- JspC.java 25 Apr 2004 11:54:04 - 1.70
+++ JspC.java 27 Apr 2004 18:04:37 - 1.71
@@ -740,15 +740,14 @@
rootCause = ((JasperException) rootCause).getRootCause();
}
log.error(Localizer.getMessage(jspc.error.generalException,
- file),
- rootCause);
+ file), rootCause);
throw je;
} catch (Exception e) {
-if ((e instanceof FileNotFoundException) log.isWarnEnabled()) {
-log.warn(Localizer.getMessage(jspc.error.fileDoesNotExist,
- e.getMessage()));
-}
+if ((e instanceof FileNotFoundException) log.isWarnEnabled()) {
+log.warn(Localizer.getMessage(jspc.error.fileDoesNotExist,
+ e.getMessage()));
+}
throw new JasperException(e);
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18479] - HttpSessionBindingListener.valueUnbound() not called
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=18479. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=18479 HttpSessionBindingListener.valueUnbound() not called --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 18:08 --- Thanks Remy, that sovled the issue! The listeners are no longer null so the attributeRemoved() method of my HttpSessionAttributeListener is now successfully called as expected. Jake - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Compiler.java
luehe 2004/04/27 11:14:13
Modified:jasper2/src/share/org/apache/jasper/compiler Compiler.java
Log:
Fixed Bugzilla 28603 (JspC Ant task does not detect errors on a
second compile):
Remove empty .java file (that was generated by new
FileOutputStream()) if parser/validator/generator throws exception.
Also removed tabs.
Revision ChangesPath
1.81 +109 -86
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java
Index: Compiler.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- Compiler.java 20 Apr 2004 20:05:19 - 1.80
+++ Compiler.java 27 Apr 2004 18:14:13 - 1.81
@@ -146,105 +146,129 @@
* @return a smap for the current JSP page, if one is generated,
* null otherwise
*/
-private String[] generateJava()
-throws Exception
-{
- String[] smapStr = null;
+private String[] generateJava() throws Exception {
+
+String[] smapStr = null;
long t1=System.currentTimeMillis();
- // Setup page info area
- pageInfo = new PageInfo(new BeanRepository(ctxt.getClassLoader(),
-errDispatcher));
-
- JspConfig jspConfig = options.getJspConfig();
- JspConfig.JspProperty jspProperty =
- jspConfig.findJspProperty(ctxt.getJspFile());
+// Setup page info area
+pageInfo = new PageInfo(new BeanRepository(ctxt.getClassLoader(),
+ errDispatcher));
+
+JspConfig jspConfig = options.getJspConfig();
+JspConfig.JspProperty jspProperty =
+jspConfig.findJspProperty(ctxt.getJspFile());
/*
* If the current uri is matched by a pattern specified in
* a jsp-property-group in web.xml, initialize pageInfo with
* those properties.
*/
-pageInfo.setELIgnored(JspUtil.booleanValue(jspProperty.isELIgnored()));
-
pageInfo.setScriptingInvalid(JspUtil.booleanValue(jspProperty.isScriptingInvalid()));
+pageInfo.setELIgnored(JspUtil.booleanValue(
+jspProperty.isELIgnored()));
+pageInfo.setScriptingInvalid(JspUtil.booleanValue(
+jspProperty.isScriptingInvalid()));
if (jspProperty.getIncludePrelude() != null) {
pageInfo.setIncludePrelude(jspProperty.getIncludePrelude());
}
- if (jspProperty.getIncludeCoda() != null) {
+if (jspProperty.getIncludeCoda() != null) {
pageInfo.setIncludeCoda(jspProperty.getIncludeCoda());
- }
+}
+
String javaFileName = ctxt.getServletJavaFileName();
+ServletWriter writer = null;
-// Setup the ServletWriter
-String javaEncoding = ctxt.getOptions().getJavaEncoding();
- OutputStreamWriter osw = null;
- try {
- osw = new OutputStreamWriter(new FileOutputStream(javaFileName),
- javaEncoding);
- } catch (UnsupportedEncodingException ex) {
-errDispatcher.jspError(jsp.error.needAlternateJavaEncoding,
javaEncoding);
- }
-
- ServletWriter writer = new ServletWriter(new PrintWriter(osw));
-ctxt.setWriter(writer);
-
-// Reset the temporary variable counter for the generator.
-JspUtil.resetTemporaryVariableName();
-
- // Parse the file
- ParserController parserCtl = new ParserController(ctxt, this);
- pageNodes = parserCtl.parse(ctxt.getJspFile());
-
- if (ctxt.isPrototypeMode()) {
- // generate prototype .java file for the tag file
- Generator.generate(writer, this, pageNodes);
-writer.close();
- return null;
- }
+try {
+// Setup the ServletWriter
+String javaEncoding = ctxt.getOptions().getJavaEncoding();
+OutputStreamWriter osw = null;
+
+try {
+osw = new OutputStreamWriter(
+new FileOutputStream(javaFileName), javaEncoding);
+} catch (UnsupportedEncodingException ex) {
+errDispatcher.jspError(jsp.error.needAlternateJavaEncoding,
+ javaEncoding);
+}
+
+writer = new ServletWriter(new PrintWriter(osw));
+ctxt.setWriter(writer);
+
+// Reset the temporary variable counter for the generator.
+JspUtil.resetTemporaryVariableName();
+
+ // Parse the
DO NOT REPLY [Bug 28603] - JspC Ant task does not detect errors on a second compile
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28603. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28603 JspC Ant task does not detect errors on a second compile [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 18:15 --- Fixed by removing empty .java file (that was generated by new FileOutputStream()) if parser/validator/generator throws exception. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28636] New: - JNDI Authorization Broken.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28636. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28636 JNDI Authorization Broken. Summary: JNDI Authorization Broken. Product: Tomcat 4 Version: 4.1.30 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have successfully used both JDBC and JNDI (backed by Active Directory) on tomcat 4.1.27, 4.1.29, and can toggle between them easily. I upgraded to 4.1.30, and the authentication portion works, but the authorization breaks. It retreives the roles successfully from the AD server. FWIW, JDBC realms work as expected. Here is the logfile from the 4.1.30 instance: 2004-04-27 14:20:58 JNDIRealm[Standalone]: Searching for USER 2004-04-27 14:20:58 JNDIRealm[Standalone]: base: OU=Users, OU=CITY,OU=USA, DC=ad,DC=COMPANY,DC=com filter: (sAMAccountName=USER) 2004-04-27 14:20:58 JNDIRealm[Standalone]: entry found for USER with dn CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: retrieving values for attribute memberOf 2004-04-27 14:20:58 JNDIRealm[Standalone]: validating credentials by binding as the user 2004-04-27 14:20:58 JNDIRealm[Standalone]: binding as CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: Username USER successfully authenticated 2004-04-27 14:20:58 JNDIRealm[Standalone]: getRoles(CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com) 2004-04-27 14:20:58 JNDIRealm[Standalone]: Searching role base 'OU=Groups, OU=CITY, OU=USA, DC=ad,DC=COMPANY,DC=com' for attribute 'cn' 2004-04-27 14:20:58 JNDIRealm[Standalone]: With filter expression '\28member=CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com\29' 2004-04-27 14:20:58 JNDIRealm[Standalone]: Returning 68 roles 2004-04-27 14:20:58 JNDIRealm[Standalone]: Found role CN=MatlibUser,OU=Groups,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: Found role CN=MatlibSysAdmin,OU=Groups,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: Found role CN=MatlibDataAdmin,OU=Groups,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: Found role CN=STP RND DEV Hippo,OU=Groups,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:20:58 JNDIRealm[Standalone]: Username USER does NOT have role MatlibUser 2004-04-27 14:20:58 JNDIRealm[Standalone]: Username USER does NOT have role STP RND AARDVARK 2004-04-27 14:20:58 JNDIRealm[Standalone]: Username USER does NOT have role STP RND DEV AEG 2004-04-27 14:20:58 JNDIRealm[Standalone]: Username USER does NOT have role all Note that it successfully retreives the roles, but for some reason claims the USER is not in the role (ie STP RND AARDVARK, STP RND DEV AEG, and MatlibUser specifically). If I use the same webapp war file, the same JNDI realm, same (cp/paste) realm config in a 4.1.29 instance, it works well. Here is the log from that: 2004-04-27 14:10:37 JNDIRealm[Standalone]: Connecting to URL ldap://LDAPSERVER.COMPANY.com 2004-04-27 14:14:10 JNDIRealm[Standalone]: Searching for USER 2004-04-27 14:14:10 JNDIRealm[Standalone]: base: OU=Users, OU=CITY, OU=USA, DC=ad,DC=COMPANY,DC=com filter: (sAMAccountName=USER) 2004-04-27 14:14:10 JNDIRealm[Standalone]: entry found for USER with dn CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:14:10 JNDIRealm[Standalone]: retrieving values for attribute memberOf 2004-04-27 14:14:10 JNDIRealm[Standalone]: validating credentials by binding as the user 2004-04-27 14:14:10 JNDIRealm[Standalone]: binding as CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com 2004-04-27 14:14:10 JNDIRealm[Standalone]: Username USER successfully authenticated 2004-04-27 14:14:11 JNDIRealm[Standalone]: getRoles(CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com) 2004-04-27 14:14:11 JNDIRealm[Standalone]: Searching role base 'OU=Groups, OU=CITY, OU=USA, DC=ad,DC=COMPANY,DC=com' for attribute 'cn' 2004-04-27 14:14:11 JNDIRealm[Standalone]: With filter expression '(member=CN=USER,OU=Users,OU=CITY,OU=USA,DC=ad,DC=COMPANY,DC=com)' 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values for attribute cn 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values for attribute cn 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values for attribute cn 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values for attribute cn 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values for attribute cn 2004-04-27 14:14:14 JNDIRealm[Standalone]: retrieving values
DO NOT REPLY [Bug 28636] - JNDI Authorization Broken in 4.1.30
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28636. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28636 JNDI Authorization Broken in 4.1.30 [EMAIL PROTECTED] changed: What|Removed |Added Summary|JNDI Authorization Broken. |JNDI Authorization Broken in ||4.1.30 --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 19:51 --- Ok, I changed my search on the mailing list and found out that this is a known issue, http://www.mail-archive.com/[EMAIL PROTECTED]/msg122940.html I'm leaving this open for now, and will let someone smarter than I close this if appropriate. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28636] - JNDI Authorization Broken in 4.1.30
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28636. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28636 JNDI Authorization Broken in 4.1.30 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 19:58 --- This is a duplicate, already been found and fixed in CVS. Unfortunately there has not been a release of the Tomcat 4.1.x series in which to receive the fix. Once I find the other defect # I'll mark this one as duplicate, and I'll also post a msg to the dev list suggesting a release. (though IANAC) Actually, it looks like there never was a bug submitted on the last issue, so I will close this as fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What is the possibility of / interest in a 4.1.31 release?
For a third time, we have had a defect logged on the fact that I introduced a bug into JNDIRealm while adding a new filtering feature. The fix was very simple and has been made, but post-release of 4.1.30. That, and the admin application largely does not work due to an unfortunate tagging problem. What is the possibility that there will be a 4.1.31 release? Is there any interest in that? I am not a committer and so cannot bring this about, but I wanted to suggest that it seems to me to be a very good idea. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the possibility of / interest in a 4.1.31 release?
Parallel question: How many think that the public messaging should be that more along the lines of Tomcat 5 is now at least as stable/mature as Tomcat 4.1.30 and that folk should upgrade to it? Having asked, I still believe a 4.1.31 for such an issue as that brought up here would be appropriate. I ask the question in terms of messaging to users, OEMs, etc, that 4.1.x has been superseded by 5.0.x in terms of the best version for production -- if/when the community feels this is reality. Personally, I feel that 5.0.22 is at least as stable as the latest 4.1.x, is faster, and overall is preferable. -- Jess Holle Jeff Tulley wrote: For a third time, we have had a defect logged on the fact that I introduced a bug into JNDIRealm while adding a new filtering feature. The fix was very simple and has been made, but post-release of 4.1.30. That, and the admin application largely does not work due to an unfortunate tagging problem. What is the possibility that there will be a 4.1.31 release? Is there any interest in that? I am not a committer and so cannot bring this about, but I wanted to suggest that it seems to me to be a very good idea. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the possibility of / interest in a 4.1.31 release?
Hi, It's unlikely you'll see a 4.1.x release for any one feature, unless it's a critical security fix. 4.1.x will have bundle releases with several features, less frequency. We've been giving the message for a while now that 5.x is the way to go, not least because less resources (including release manager resources) are spent on 4.x. Yoav Shapira Millennium Research Informatics -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 4:36 PM To: Tomcat Developers List Subject: Re: What is the possibility of / interest in a 4.1.31 release? Parallel question: How many think that the public messaging should be that more along the lines of Tomcat 5 is now at least as stable/mature as Tomcat 4.1.30 and that folk should upgrade to it? Having asked, I still believe a 4.1.31 for such an issue as that brought up here would be appropriate. I ask the question in terms of messaging to users, OEMs, etc, that 4.1.x has been superseded by 5.0.x in terms of the best version for production -- if/when the community feels this is reality. Personally, I feel that 5.0.22 is at least as stable as the latest 4.1.x, is faster, and overall is preferable. -- Jess Holle Jeff Tulley wrote: For a third time, we have had a defect logged on the fact that I introduced a bug into JNDIRealm while adding a new filtering feature. The fix was very simple and has been made, but post-release of 4.1.30. That, and the admin application largely does not work due to an unfortunate tagging problem. What is the possibility that there will be a 4.1.31 release? Is there any interest in that? I am not a committer and so cannot bring this about, but I wanted to suggest that it seems to me to be a very good idea. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context SaveContextAction.java
markt 2004/04/27 13:54:48
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context
SaveContextAction.java
Log:
- Fix bug 18383. Admin app should set path to rather than / for a new root
context.
The path in the mbean name still needs to be / to prevent naming error.
- Removed unused imports identified by Eclipse.
Revision ChangesPath
1.12 +11 -14
jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/SaveContextAction.java
Index: SaveContextAction.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/SaveContextAction.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- SaveContextAction.java14 Mar 2003 16:00:16 - 1.11
+++ SaveContextAction.java27 Apr 2004 20:54:48 - 1.12
@@ -63,17 +63,11 @@
import java.net.URLEncoder;
-import java.util.Iterator;
import java.util.Locale;
import java.io.IOException;
import javax.management.Attribute;
import javax.management.MBeanServer;
-import javax.management.MBeanServerFactory;
-import javax.management.QueryExp;
-import javax.management.Query;
-import javax.management.ObjectInstance;
import javax.management.ObjectName;
-import javax.management.JMException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
@@ -185,10 +179,13 @@
String cObjectName = cform.getObjectName();
String lObjectName = cform.getLoaderObjectName();
String mObjectName = cform.getManagerObjectName();
+String oNamePath = ;
if ((cform.getPath() == null) || (cform.getPath().length()1)) {
-cform.setPath(/);
+oNamePath = (/);
+} else {
+oNamePath = cform.getPath();
}
-
+
// Perform a Create Context transaction (if requested)
if (Create.equals(adminAction)) {
@@ -203,7 +200,7 @@
// Ensure that the requested context name is unique
ObjectName oname =
new ObjectName(TomcatTreeBuilder.CONTEXT_TYPE +
- ,path= + cform.getPath() +
+ ,path= + oNamePath +
,host= + honame.getKeyProperty(host) +
,service= + honame.getKeyProperty(service));
@@ -222,7 +219,7 @@
// Create a new StandardContext object
values = new Object[3];
values[0] = parentName;
-values[1] = cform.getPath();
+values[1] = oNamePath;
values[2] = cform.getDocBase();
operation = createStandardContext;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18383] - context path is set to / instead of
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=18383. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=18383 context path is set to / instead of [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 20:56 --- This has been fixed in CVS. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the possibility of / interest in a 4.1.31 release?
Glad to hear it. Perhaps I'm dense, but this stance is not readily apparent from the Tomcat web page. Contrast: *Tomcat 4.0.x*. Tomcat 4.0.6 is the old production quality release... with *Tomcat 4.1.x*. Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and contains significant enhancements, including... Perhaps Tomcat 4.1.x's verbage should be more like Tomcat 4.0.x's, i.e. state that it is an old production quality release... -- Jess Holle Shapira, Yoav wrote: Hi, It's unlikely you'll see a 4.1.x release for any one feature, unless it's a critical security fix. 4.1.x will have bundle releases with several features, less frequency. We've been giving the message for a while now that 5.x is the way to go, not least because less resources (including release manager resources) are spent on 4.x. Yoav Shapira Millennium Research Informatics -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 4:36 PM To: Tomcat Developers List Subject: Re: What is the possibility of / interest in a 4.1.31 release? Parallel question: How many think that the public messaging should be that more along the lines of Tomcat 5 is now at least as stable/mature as Tomcat 4.1.30 and that folk should upgrade to it? Having asked, I still believe a 4.1.31 for such an issue as that brought up here would be appropriate. I ask the question in terms of messaging to users, OEMs, etc, that 4.1.x has been superseded by 5.0.x in terms of the best version for production -- if/when the community feels this is reality. Personally, I feel that 5.0.22 is at least as stable as the latest 4.1.x, is faster, and overall is preferable. -- Jess Holle Jeff Tulley wrote: For a third time, we have had a defect logged on the fact that I introduced a bug into JNDIRealm while adding a new filtering feature. The fix was very simple and has been made, but post-release of 4.1.30. That, and the admin application largely does not work due to an unfortunate tagging problem. What is the possibility that there will be a 4.1.31 release? Is there any interest in that? I am not a committer and so cannot bring this about, but I wanted to suggest that it seems to me to be a very good idea. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspC.java
luehe 2004/04/27 14:40:21
Modified:jasper2/src/share/org/apache/jasper JspC.java
Log:
Fixed Bugzilla 28604 (JspC should not display the whole stack trace
of errors)
Print rootcause's stack trace only if rootcause is different from JasperException
Revision ChangesPath
1.72 +3 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- JspC.java 27 Apr 2004 18:04:37 - 1.71
+++ JspC.java 27 Apr 2004 21:40:21 - 1.72
@@ -739,8 +739,6 @@
((JasperException) rootCause).getRootCause() != null) {
rootCause = ((JasperException) rootCause).getRootCause();
}
-log.error(Localizer.getMessage(jspc.error.generalException,
- file), rootCause);
throw je;
} catch (Exception e) {
@@ -863,7 +861,9 @@
((JasperException) rootCause).getRootCause() != null) {
rootCause = ((JasperException) rootCause).getRootCause();
}
-rootCause.printStackTrace();
+if (rootCause != je) {
+rootCause.printStackTrace();
+}
throw je;
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
WebappClassLoader: Lifecycle error : CL stopped
All, I have been looking at a couple of bugs in the admin app and have come across a problem with creating new hosts and contexts. The scenario is: 1. Create new host 2. Create new root context for the new host 3. Try to access jsp in new root context This gives causes the WebappClassLoader: Lifecycle error : CL stopped error. AFAICT the problem occurs during step 2. - The admin app creates the conext - The context inherits a classloader from the host - The context starts the jsp servlet which creates a JspRuntimeContext - JspRuntimeContext retains a reference to the context classloader - The admin app creates a classloader for the context and sets it - The old context classloader is stopped and the new one started - Subsequent requests for jsps fail because the context classloader referred to by JspRuntimeContext has been stopped Restarting tomcat fixes this issue as the classloaders are set before the context is started. Options for fixing this are (I haven't look at the code for any of these): - Do nothing and require the users to restart - Change the admin app to restart the context after changing the loader - Modify jasper to check the status of the classloader - Separate the creating and starting of components through mbeans I don't really like any of these options. Does anyone have any better ideas? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WebappClassLoader: Lifecycle error : CL stopped
Hi, Options for fixing this are (I haven't look at the code for any of these): - Do nothing and require the users to restart - Change the admin app to restart the context after changing the loader - Modify jasper to check the status of the classloader - Separate the creating and starting of components through mbeans I don't really like any of these options. Does anyone have any better ideas? I like #2: in fact, it seems like it should be strictly enforced for general stability and security, and I'm surprised the current code doesn't restart a context after changing its loader already. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20691] - Fails to work when new host is added in server.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=20691. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=20691 Fails to work when new host is added in server.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 21:47 --- This has been fixed in CVS. The issue appears to be similar to bug 18383. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WebappClassLoader: Lifecycle error : CL stopped
Shapira, Yoav wrote: Hi, I like #2: in fact, it seems like it should be strictly enforced for general stability and security, and I'm surprised the current code doesn't restart a context after changing its loader already. I think the admin webapp should stop the context before doing anything to its loader (and then start it again if it wants to). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the possibility of / interest in a 4.1.31 release?
So what I've brought up is not a critical security fix, but instead a critical functionality fix, with a workaround that is quite annoying for end users. How does that rate? Yes, Tomcat 5.x is the way to go, but for instance on support packs for NetWare we are not at liberty to make such a big move, but instead need to make the smaller upgrade of 4.1.29 to 4.1.30. I will pull in whatever additional fixes I need(JNDIRealm, the Connector to make the admin work), but the story of Move to 5.x does not fit everybody's case. But, the next major release vehicle of NetWare and our Novell Linux Services will do that move to the 5.x code of course. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com [EMAIL PROTECTED] 4/27/04 2:49:32 PM Hi, It's unlikely you'll see a 4.1.x release for any one feature, unless it's a critical security fix. 4.1.x will have bundle releases with several features, less frequency. We've been giving the message for a while now that 5.x is the way to go, not least because less resources (including release manager resources) are spent on 4.x. Yoav Shapira Millennium Research Informatics -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 4:36 PM To: Tomcat Developers List Subject: Re: What is the possibility of / interest in a 4.1.31 release? Parallel question: How many think that the public messaging should be that more along the lines of Tomcat 5 is now at least as stable/mature as Tomcat 4.1.30 and that folk should upgrade to it? Having asked, I still believe a 4.1.31 for such an issue as that brought up here would be appropriate. I ask the question in terms of messaging to users, OEMs, etc, that 4.1.x has been superseded by 5.0.x in terms of the best version for production -- if/when the community feels this is reality. Personally, I feel that 5.0.22 is at least as stable as the latest 4.1.x, is faster, and overall is preferable. -- Jess Holle Jeff Tulley wrote: For a third time, we have had a defect logged on the fact that I introduced a bug into JNDIRealm while adding a new filtering feature. The fix was very simple and has been made, but post-release of 4.1.30. That, and the admin application largely does not work due to an unfortunate tagging problem. What is the possibility that there will be a 4.1.31 release? Is there any interest in that? I am not a committer and so cannot bring this about, but I wanted to suggest that it seems to me to be a very good idea. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28631. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28631 JAASRealm fix to permit user-specified user/group Principals --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 22:39 --- I should make clear that the patch files I submitted affect 5.0.19, but were diffed against those from CVS HEAD, on the morning of 4/14/2004. Sorry if that was not readily apparent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Administraçao Toto Bola
Prezado(a) usuário, Devido a incidencia exagerada de emails recebidos com vírus, o endereço [EMAIL PROTECTED] foi trocado para [EMAIL PROTECTED]. Por favor, encaminhe sua dúvida ou mensagem para o novo endereço que logo responderemos. Obrigado, Administração [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 tomcat.nsi
markt 2004/04/27 15:41:50 Modified:.tomcat.nsi Log: Fix bug 20709. Use same setting for 'Djava.endorsed.dirs' when starting via menu as for service and batch file. Revision ChangesPath 1.35 +2 -2 jakarta-tomcat-4.0/tomcat.nsi Index: tomcat.nsi === RCS file: /home/cvs/jakarta-tomcat-4.0/tomcat.nsi,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- tomcat.nsi6 Oct 2003 12:23:19 - 1.34 +++ tomcat.nsi27 Apr 2004 22:41:50 - 1.35 @@ -115,7 +115,7 @@ CreateShortCut $SMPROGRAMS\Apache Tomcat 4.1\Start Tomcat.lnk \ $2\bin\java.exe \ - '-jar -Duser.dir=$INSTDIR $INSTDIR\bin\bootstrap.jar start' \ + '-jar -Duser.dir=$INSTDIR -Djava.endorsed.dirs=$INSTDIR\common\endorsed $INSTDIR\bin\bootstrap.jar start' \ $INSTDIR\tomcat.ico 0 SW_SHOWNORMAL CreateShortCut $SMPROGRAMS\Apache Tomcat 4.1\Stop Tomcat.lnk \ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20709] - start menu for tomcat doesn't include java.endorsed.dirs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=20709. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=20709 start menu for tomcat doesn't include java.endorsed.dirs [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 22:42 --- This has been fixed in CVS. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the possibility of / interest in a 4.1.31 release?
Hi, So what I've brought up is not a critical security fix, but instead a critical functionality fix, with a workaround that is quite annoying for end users. How does that rate? Below a critical security fix. Personally, I wouldn't rate the JNDIRealm as a critical piece of functionality either, but that's a simple and subjective opinion based solely on its rarity as an issue on the tomcat-user list. Yes, Tomcat 5.x is the way to go, but for instance on support packs for NetWare we are not at liberty to make such a big move, but instead need to make the smaller upgrade of 4.1.29 to 4.1.30. I will pull in whatever additional fixes I need(JNDIRealm, the Connector to make the admin work), but the story of Move to 5.x does not fit everybody's case. I understand completely, and I further imagine there are other people who can't move to 5.x for other reasons (support contracts, 3rd party library lock-in, 4.x-specific code, etc). What I said earlier holds just the same. Your fix will not be ignored forever: it will be bundled into the next 4.x release. But because there is no established frequency on releases for a maintenance-phase branch, if you need your fix now you have to do a custom build. This policy is not dramatically different from other products, both in the open-source and in the commercial software realms. If you found a functionality (not security) bug in Excel 97, you'd be told to upgrade as that's in maintenance-mode. In fact I think we've been pretty good in maintaining 4.x and doing a couple of releases even after 5.x stable came out. But, the next major release vehicle of NetWare and our Novell Linux Services will do that move to the 5.x code of course. Cool. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets ManagerServlet.java
markt 2004/04/27 15:55:10
Modified:catalina/src/share/org/apache/catalina/servlets
ManagerServlet.java
Log:
- Fix bug 20786. Manger webapp session output not formatted correctly
for session inactive for 10 minutes.
- Remove unused imports identified by Ecipse.
Revision ChangesPath
1.33 +5 -7
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/ManagerServlet.java
Index: ManagerServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/ManagerServlet.java,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- ManagerServlet.java 14 Jan 2003 23:28:29 - 1.32
+++ ManagerServlet.java 27 Apr 2004 22:55:10 - 1.33
@@ -73,7 +73,6 @@
import java.io.PrintWriter;
import java.net.URL;
import java.net.MalformedURLException;
-import java.util.Enumeration;
import java.util.Iterator;
import java.util.Locale;
import java.util.jar.JarEntry;
@@ -89,7 +88,6 @@
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
-import org.apache.catalina.Container;
import org.apache.catalina.ContainerServlet;
import org.apache.catalina.Context;
import org.apache.catalina.Deployer;
@@ -1055,7 +1053,7 @@
}
if (timeout[0] 0)
writer.println(sm.getString(managerServlet.sessiontimeout,
-10 + timeout[0]));
+10, + timeout[0]));
for (int i = 1; i timeout.length-1; i++) {
if (timeout[i] 0)
writer.println(sm.getString(managerServlet.sessiontimeout,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/manager/WEB-INF/classes/org/apache/catalina/manager ManagerServlet.java
markt 2004/04/27 16:02:24
Modified:webapps/manager/WEB-INF/classes/org/apache/catalina/manager
ManagerServlet.java
Log:
- Fix bug 20786. Manger webapp session output not formatted correctly
for session inactive for 10 minutes.
- Remove unused imports identified by Ecipse.
- Ported from TC4.
Revision ChangesPath
1.18 +2 -3
jakarta-tomcat-catalina/webapps/manager/WEB-INF/classes/org/apache/catalina/manager/ManagerServlet.java
Index: ManagerServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/webapps/manager/WEB-INF/classes/org/apache/catalina/manager/ManagerServlet.java,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- ManagerServlet.java 12 Apr 2004 22:05:49 - 1.17
+++ ManagerServlet.java 27 Apr 2004 23:02:24 - 1.18
@@ -28,7 +28,6 @@
import java.io.PrintWriter;
import java.net.URL;
import java.net.MalformedURLException;
-import java.util.Enumeration;
import java.util.Iterator;
import java.util.jar.JarEntry;
import java.util.jar.JarFile;
@@ -1271,7 +1270,7 @@
}
if (timeout[0] 0)
writer.println(sm.getString(managerServlet.sessiontimeout,
-10 + timeout[0]));
+10, + timeout[0]));
for (int i = 1; i timeout.length-1; i++) {
if (timeout[i] 0)
writer.println(sm.getString(managerServlet.sessiontimeout,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20786] - Incorrect output of session information
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=20786. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=20786 Incorrect output of session information [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-27 23:03 --- This has been fixed in CVS for tomcat 4 and tomcat 5. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the possibility of / interest in a 4.1.31 release?
So what I've brought up is not a critical security fix, but instead a critical functionality fix, with a workaround that is quite annoying for end users. How does that rate? Below a critical security fix. Personally, I wouldn't rate the JNDIRealm as a critical piece of functionality either, but that's a simple and subjective opinion based solely on its rarity as an issue on the tomcat-user list. Oh, Yoav - I was talking about the admin piece not working as the critical piece of functionality. No, the JNDIRealm issue is minor, it just keeps coming up. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28604] - JspC should not display the whole stack trace of errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28604. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28604 JspC should not display the whole stack trace of errors [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-28 00:43 --- Print rootcause's stack trace only if rootcause is different from JasperException - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources ResourceUtils.java
amyroh 2004/04/27 19:02:46
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources
ResourceUtils.java
Log:
Fix for 28524 - Exception throw when creating new JNDI data source.
Revision ChangesPath
1.9 +11 -2
jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources/ResourceUtils.java
Index: ResourceUtils.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources/ResourceUtils.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ResourceUtils.java27 Feb 2004 14:59:04 - 1.8
+++ ResourceUtils.java28 Apr 2004 02:02:46 - 1.9
@@ -22,10 +22,12 @@
import java.util.Iterator;
import java.util.Collections;
+import javax.management.AttributeNotFoundException;
import javax.management.MBeanServer;
import javax.management.ObjectName;
import javax.management.ObjectInstance;
+
/**
* pShared utility methods for the resource administration module./p
*
@@ -197,7 +199,14 @@
while (iterator.hasNext()) {
ObjectInstance instance = (ObjectInstance) iterator.next();
-results.add(instance.getObjectName().toString());
+ObjectName oname = instance.getObjectName();
+try {
+// only add resource mbean if definition exists
+mserver.getAttribute(oname, driverClassName);
+results.add(instance.getObjectName().toString());
+} catch (AttributeNotFoundException ex) {
+// full resource definition doesn't exist
+}
}
Collections.sort(results);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28524. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-04-28 02:05 --- Fixed - doesn't try to display context resource in admin unless you have full resource definition in your context.xml or server.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@lsd]: jakarta-tomcat-5/jakarta-tomcat-5 failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project jakarta-tomcat-5 has an issue affecting its community integration, and has been outstanding for 18 runs. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/jakarta-tomcat-5/jakarta-tomcat-5/index.html That said, some snippets follow: Gump provided these annotations: - Info - Jar [servlets-default.jar] identifier set to jar basename: [servlets-default] - Info - Jar [naming-common.jar] identifier set to jar basename: [naming-common] - Info - Jar [naming-resources.jar] identifier set to jar basename: [naming-resources] - Info - Jar [catalina.jar] identifier set to jar basename: [catalina] - Info - Jar [bootstrap.jar] identifier set to jar basename: [bootstrap] - Info - Jar [servlets-common.jar] identifier set to jar basename: [servlets-common] - Info - Jar [servlets-invoker.jar] identifier set to jar basename: [servlets-invoker] - Info - Dependency on javamail exists, no need to add for property mail.jar. - Info - Dependency on jaf exists, no need to add for property activation.jar. - Info - Dependency on jakarta-servletapi-5-servlet exists, no need to add for property servlet-api.jar. - Info - Dependency on jakarta-servletapi-5-jsp exists, no need to add for property jsp-api.jar. - Info - Dependency on xml-xerces exists, no need to add for property xercesImpl.jar. - Info - Dependency on xml-xerces exists, no need to add for property xmlParserAPIs.jar. - Info - Dependency on jakarta-tomcat-util exists, no need to add for property tomcat-util.jar. - Info - Dependency on commons-el exists, no need to add for property commons-el.jar. - Info - Dependency on commons-logging exists, no need to add for property commons-logging-api.jar. - Info - Dependency on commons-modeler exists, no need to add for property commons-modeler.jar. - Info - Dependency on ant exists, no need to add for property ant.home. - Info - Dependency on jsse exists, no need to add for property jsse.home. - Info - Dependency on jmx exists, no need to add for property jmx.home. - Info - Dependency on jmx exists, no need to add for property jmx.jar. - Info - Dependency on jmx exists, no need to add for property jmx-tools.jar. - Info - Dependency on jndi exists, no need to add for property jndi.home. - Info - Dependency on jakarta-regexp exists, no need to add for property regexp.home. - Info - Dependency on jakarta-regexp exists, no need to add for property regexp.jar. - Info - Dependency on javamail exists, no need to add for property mail.home. - Info - Dependency on jakarta-tomcat-coyote exists, no need to add for property tomcat-coyote.home. - Info - Dependency on jakarta-tomcat-jasper_tc5 exists, no need to add for property jasper.home. - Info - Dependency on jaf exists, no need to add for property activation.home. - Info - Dependency on commons-modeler exists, no need to add for property commons-modeler.home. - Info - Dependency on commons-daemon exists, no need to add for property commons-daemon.jsvc.tar.gz. - Info - Dependency on jakarta-struts exists, no need to add for property struts.home. - Info - Enable debug output, due to a sequence of 17 previous errors. - Info - Failed with reason build failed Gump performed this work: http://lsd.student.utwente.nl/gump/jakarta-tomcat-5/jakarta-tomcat-5/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-5.html Work Name: build_jakarta-tomcat-5_jakarta-tomcat-5 (Type: Build) State: Failed Elapsed: 0 hours, 1 minutes, 57 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar:/data3/gump/xml-xalan/java/build/xalan-unbundled.jar:/data3/gump/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -debug -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dtomcat33.home=*Unset* -Djsp-api.jar=/data3/gump/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar -Dtomcat-coyote.home=/data3/gump/jakarta-tomcat-connectors/coyote -Djndi.jar=/data3/gump/opt/jndi1_2_1/lib/jndi.jar -Dsite2.home=/data3/gump/jakarta-site2 -DxmlParserAPIs.jar=/data3/gump/xml-xerces2/java/build/xercesImpl.jar -Dactivation.home=/data3/gump/opt/jaf-1.0.1 -Djmx.home=/data3/gump/opt/jmx-1_2-ri -Djdbc20ext.jar=/data3/gump/opt/jdbc2_0/jdbc2_0-stdext.jar -Djmx-tools.jar=/data3/gump/opt/jmx-1_2-ri/lib/jmxtools.jar -Dregexp.jar=/data3/gump/jakarta-regexp/build/jakarta-regexp-20040428.jar -Dmail.home=/data3/gump/opt/javamail-1.3 -Dant.home=/data3/gump/ant/dist -Dcommons-modeler.home=/data3/gump/jakarta-commons/modeler -Dcommons-launcher.jar=/data3/gump/jakarta-commons/launcher/dist/bin/commons-launcher.jar
Administraçao Toto Bola
Prezado(a) usuário, Devido a incidencia exagerada de emails recebidos com vírus, o endereço [EMAIL PROTECTED] foi trocado para [EMAIL PROTECTED]. Por favor, encaminhe sua dúvida ou mensagem para o novo endereço que logo responderemos. Obrigado, Administração [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
