Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java
[EMAIL PROTECTED] wrote: amyroh 2003/11/24 15:01:22 Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java Log: Add getters for all attributes defined in MBeanInfo so getAttribute calls suceed. Doing this is not good: these are attributes of the thread pool, not of the protocol. I believe each one has its MBean, so there's no problem. I will not integrate your last two patches in my 5.0.15 tag. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Justification for URIEncoding addition?
Hans Bergsten wrote: Remy Maucherat wrote: Hans Bergsten wrote: Larry Isaacs wrote: Hans, The behavior change is unrelated to the use of getParameter() to search for jsp_precompile. Both Tomcat 3.x and Tomcat 4.x were bit by this log ago and Craig's fix was applied to both. In Tomcat 4's case, it was prior to the 4.0 release. Okay, I'm sure you're right that there may be more to it than avoiding the getParameter() call in Jasper, but based on what I've read, it seems to be part of the problem at least. Assuming I have a good grip on the issue, I think it relates to using UTF-8 to decode the path portion of the URL which gets used to determine context, servlet mapping, etc. Then allowing setCharacterEncoding() to change the character encoding for the query portion of the same URL. The Servlet 2.3 and 2.4 specs both say setCharacterEncoding() applies to the request body but don't mention it applying to the query portion of the URL. Right, but since the servlet spec doesn't say anything about encoding for the query portion, I think we have some room for a sensible interpretation. My concern is that with the new decoding behavior, apps that used to work fine suddenly don't, and the reason seems to be that browsers in fact ignore the RFC2718 recommendation that TC now enforces. I'm all for compliance with all related specs, but in this case it's just a recommendation and following it seems to do more harm than good. I agree it's not as clean as you may want, but are there any real problems with decoding the path portion using one charset and the query string with another (i.e., the one from getCharacterEncoding()), the way it used to be done? I see you as a member of the expert group for the servlet spec. Did you make out those points during the review period ? If not, then you IMO have nothing to complain about, esp since Tomcat implements a far more reasonable and simpler behavior for the URL string handling. Remy, I'm not complaining, I'm just trying to help with ideas for how solve a problem that apparently affects a lot of people. Sigh! Yes, I'm in the servlet spec EG and I did help solving other i18n problems by bringing together all the spec leads for servlets, JSP and JSTL and Sun's i18n guru to fix inconsistencies between these specs. Unfortunately, I missed the query string encoding problem, largely because the way TC handled it before the recent change seemed to work for most apps so I hadn't encountered the problem. My bad. The specification should have specified something along the lines of: - The URL must be %xx encoded - This decodes to bytes reprensenting UTF-8 characters There's an IETF standard that, I think, states this in BW. It is being ignored. Maybe this wouldn't be the case if very popular tech, such as servlets JSPs, started mandating it ? This is simply a chiken egg issue. And because its a chicken and egg problem, I doubt that it will ever be solved. No server vendor is likely to change the behavior in a way that's incompatible with a large set of browsers. A more sensible way to solve this would be for W3C to change the spec to require the behavior most browsers already implement, even if it's less elegant. i18n issues with HTTP and srevlets have been known about for years, but unfortunately they still haven't been addressed properly. Same with the request dispatcher + wrapping issues that I have pointed out months ago (and of course, were silently ignored). To balance this a little, among the other big issues, I have to give credit for solving the welcome files in a satisfactory way, as well as filters with RDs. Filters now make the proprietary APIs provided by the container irrelevant for most tasks. I'm glad you like something in the new spec ;-) Although, there's more to be done with the welcome file mechanism. I tried to get it all done in 2.4, but we couldn't reach consensus so what there now is still too vague, IMHO. I think I saw your proposal (at least I saw a radical refactoring of the feature), and I was *really* mad about it. I'm very very glad it got killed. Sorry, but I completely disagree with *all* the points you make in this email. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session StandardSession.java
remm2003/11/24 23:56:27
Modified:catalina/src/share/org/apache/catalina/session
StandardSession.java
Log:
- It seems that, for consistency, getLastAccessedTime should not throw an
ISE while expiring. This allows addressing bug 9077.
- Patch submitted by Brian Stansberry.
Revision ChangesPath
1.25 +7 -8
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardSession.java
Index: StandardSession.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardSession.java,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- StandardSession.java 3 Oct 2003 01:53:17 - 1.24
+++ StandardSession.java 25 Nov 2003 07:56:27 - 1.25
@@ -443,10 +443,9 @@
* a value associated with the session, do not affect the access time.
*/
public long getLastAccessedTime() {
-if ( !isValid ) {
-throw new IllegalStateException(
-sm.getString(standardSession.getLastAccessedTime));
-
+if ( !isValid() ) {
+throw new IllegalStateException
+(sm.getString(standardSession.getLastAccessedTime.ise));
}
return (this.lastAccessedTime);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator SingleSignOn.java
remm2003/11/25 00:02:05
Modified:catalina/src/share/org/apache/catalina/authenticator
SingleSignOn.java
Log:
- Fix bug 9077. When a session timeouts, it won't logout of all webapps
(which otherwise makes SSO quite useless).
- Patch submitted by Brian Stansberry.
Revision ChangesPath
1.11 +52 -7
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/SingleSignOn.java
Index: SingleSignOn.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/SingleSignOn.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- SingleSignOn.java 24 Nov 2003 21:28:22 - 1.10
+++ SingleSignOn.java 25 Nov 2003 08:02:05 - 1.11
@@ -376,9 +376,19 @@
if (ssoId == null)
return;
-// FIXME: Find a way to deregister only a single session in case of
-// a timeout
-deregister(ssoId);
+// Was the session destroyed as the result of a timeout?
+// If so, we'll just remove the expired session from the
+// SSO. If the session was logged out, we'll log out
+// of all session associated with the SSO.
+if (System.currentTimeMillis() - session.getLastAccessedTime() =
+session.getMaxInactiveInterval() * 1000) {
+removeSession(ssoId, session);
+} else {
+// The session was logged out.
+// Deregister this single session id, invalidating
+// associated sessions
+deregister(ssoId);
+}
}
@@ -671,6 +681,41 @@
}
//-- Package-Protected Methods
+
+
+/**
+ * Remove a single Session from a SingleSignOn. Called when
+ * a session is timed out and no longer active.
+ *
+ * @param ssoId Single sign on identifier from which to remove the session.
+ * @param session the session to be removed.
+ */
+void removeSession(String ssoId, Session session) {
+
+if (debug = 1)
+log(Removing session + session.toString() + from sso id +
+ssoId );
+
+// Get a reference to the SingleSignOn
+SingleSignOnEntry entry = lookup(ssoId);
+if (entry == null)
+return;
+
+// Remove the inactive session from SingleSignOnEntry
+entry.removeSession(session);
+
+// Remove the inactive session from the 'reverse' Map.
+synchronized(reverse) {
+reverse.remove(session);
+}
+
+// If there are not sessions left in the SingleSignOnEntry,
+// deregister the entry.
+if (entry.findSessions().length == 0) {
+deregister(ssoId);
+}
+}
+
/**
* Updates any codeSingleSignOnEntry/code found under key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAASCallbackHandler clear password in the log file
Hi, I agree with you but : 1- Even if I trust the administrator of this production environment, I'm not beyond making a mistake : the administrator may be dishonest and then can get the login and passwords and ruse them (the action he does awould then appear as normal one). 2- In no system the administrator can see the password of a user. He can only reset it (such an action produces a log). 3- I think the the JAAS realm is the only one which produces such logs. So if it is normal why the other realms (JDBC, JNDI...) wouldn't do the same ? Yann From: Tim Funk [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JAASCallbackHandler clear password in the log file Date: Mon, 24 Nov 2003 08:51:07 -0500 IMO, no. In a production environment: 1) The debug should not turned up that high 2) If its a production box, file permissions as well as people able to log into the box should be trusted. -Tim Yann GUEVEL wrote: Hi, if the debug level is 3, the org.apache.catalina.realm.JAASCallbackHandler.handle method writes in the log file the login and password it received (tomcat 4.1.29 JAASCallbackHandler.java, line 155). So any people who can access the machine on which Tomcat is running can see all the login and passwords used. Isn't this unsafe ? Should'nt this log be removed ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java
[EMAIL PROTECTED] wrote: amyroh 2003/11/24 15:01:22 Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java Log: Add getters for all attributes defined in MBeanInfo so getAttribute calls suceed. Rectification: I'll integrate your patch, but it would be best to remove the fields which are duplicated with the thread pool MBean. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/tester/web/golden JspDoc02.txt
remm2003/11/25 00:31:55 Modified:tester/web/golden JspDoc02.txt Log: - The latest updates to Jasper make it generate extra CRLF with XML, apparently. There's no actual difference, so I'm updating the golden file. Revision ChangesPath 1.2 +11 -3 jakarta-tomcat-catalina/tester/web/golden/JspDoc02.txt Index: JspDoc02.txt === RCS file: /home/cvs/jakarta-tomcat-catalina/tester/web/golden/JspDoc02.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- JspDoc02.txt 19 Aug 2003 16:04:56 - 1.1 +++ JspDoc02.txt 25 Nov 2003 08:31:55 - 1.2 @@ -1,6 +1,14 @@ htmlheadtitleExample JSP in XML format/title/headbody -This is the output of a simple JSP using XML format. br/divUse a jsp:scriptlet to loop from 1 to 10: /div1, 2, 3, 4, 5, 6, 7, 8, 9, 10 - brbrdiv align=left - Use a jsp:expression to write something: foo/div +This is the output of a simple JSP using XML format. +br/divUse a jsp:scriptlet to loop from 1 to 10: /div1, 2, 3, 4, 5, 6, 7, 8, 9, 10 + + + + brbr + + +div align=left + Use a jsp:expression to write something: + foo/div pThis sentence is enclosed in a jsp:text element./p /body/html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24965] New: - IllegalArgumentException during parsing of web.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24965. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24965 IllegalArgumentException during parsing of web.xml Summary: IllegalArgumentException during parsing of web.xml Product: Tomcat 5 Version: 5.0.14 Platform: All URL: http://www.mail-archive.com/tomcat- [EMAIL PROTECTED]/msg49455.html OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] No answer on mailing list, so create the bug. With the new 2.4 schema for servlets, there is not anymore a strict order for the top level elements in the web.xml file So we can declare a servlet and then its mapping, and then a new servlet with its mapping Something like that : servlet ...servletA../servlet servlet-mapping..servletA.../servlet-mapping servlet ...servletB../servlet servlet-mapping..servletB.../servlet-mapping But the mapping of a servlet can be declared before the declaration of the servlet element. (with 2.4 schema) servlet-mapping..servletA.../servlet-mapping servlet ...servletA../servlet The problem is that this is a valid XML but it fails during the deployment on Tomcat 5. This is due to the fact that during the XML parsing, when we add a servlet mapping, there is a check to see if the servlet exists. Note that the xml validation is turned on. The problem come from the method addServletMapping() in org.apache.catalina.core.StandardContext class. // Validate the proposed mapping if (findChild(name) == null) throw new IllegalArgumentException (sm.getString(standardContext.servletMap.name, name)); Maybe the check has to move to another place. At runtime it gives this trace when deploying the war : ContextConfig.applicationConfig : Parse error in application web.xml java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name Test at org.apache.commons.digester.Digester.createSAXException(Digester.java:2540) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2566) at org.apache.commons.digester.Digester.endElement(Digester.java:1061) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:305) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:748) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:257) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.ja - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24965] - IllegalArgumentException during parsing of web.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24965. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24965 IllegalArgumentException during parsing of web.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 10:02 --- Due to the algorithms used to initialize Catalina's mapper, this issue cannot and will not be fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 12:27 AM Subject: Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java [EMAIL PROTECTED] wrote: amyroh 2003/11/24 15:01:22 Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java Log: Add getters for all attributes defined in MBeanInfo so getAttribute calls suceed. Rectification: I'll integrate your patch, but it would be best to remove the fields which are duplicated with the thread pool MBean. +1. While I'm totally swamped right now to be able to properly review Amy's original patch, the Endpoint is not the place for doing this type of JMX configs. Rémy - 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]
Implementing a custom session manager for reauthentication
I am currently involved in a project using tomcat 4.1.29 and forms-based authentication. I would appreciate some feedback on our approach to one of our requirements and conclusions about the design of the existing code. We have a requirement to implement a reauthentication timeout separate from the session timeout, i.e. after say 5 minutes a user must re-enter their credentials in order to continue with their session, which would have a longer timeout. We've tried doing this in filters without much success, and decided that we needed to extend the container instead. Looking at the authenticator code, it appears that the way to force (re)authentication without loosing the session is to ensure that the session getPrincipal() routine returns null. So we need to somehow set the principal to null on reauthentication timeout. In order to achieve this, one of two approaches came to mind in examining the manager and session code. Our goal was to try and use as much as possible of the existing code and extend cleanly. 1. Develop our own session class that implements this behaviour. We started by considering a delegating instance of StandardSession that would perform the reauthentication check as part of getPrincipal(). However, looking at the session managers available, StandardSession is endemic in the code suggesting that extension of session was not big on the designers radar, particularly given its use in casts and session object creation. 2. Extend the manager of choice and add our own thread to set the principal to null on reauthentication timeout. There's a few hairs on this one a) The existing managers already implement runnable for session timeout, but we figure an inner class will probably do the trick for our thread b) We'll need to implement the lifecycle events to control our thread as well as the superclass thread c) The Session setPrincipal() method is not synchronised, so the possibility exists for race conditions between our thread and other code d) Managers such as StandardManager have hardcoded strings for string resources and the thread name, rather than basing these on the protected name member. Although we can change the name in our subclass constructor, we'd still end up with a thread called StandardManager... even though we're actually using our manager. I'm happy to submit a patch if changing this situation is considered appropriate. We're pursuing 2) at the moment, but would like to get the opinions on the points above from those who know the code base better. Regards Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24968] New: - RELEASE-NOTES states wrong version of commons-dbcp
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968 RELEASE-NOTES states wrong version of commons-dbcp Summary: RELEASE-NOTES states wrong version of commons-dbcp Product: Tomcat 5 Version: 5.0.14 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Documentation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RELEASE-NOTES says commons-dbcp 1.0 is provided. Version 1.1 is actually present. Would have saved me a download. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24968] - RELEASE-NOTES states wrong version of commons-dbcp
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968 RELEASE-NOTES states wrong version of commons-dbcp [EMAIL PROTECTED] changed: What|Removed |Added Summary|RELEASE-NOTES states wrong |RELEASE-NOTES states wrong |version of commons-dbcp |version of commons-dbcp --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 11:53 --- While I'm at it, you could also note what version of xercesImpl.jar is included, i.e. v2.5, since it is not immediately obvious from the jar which version it is and since it is subject of a bug in the server.xml xml validation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24970] New: - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* Summary: charset appended to content-type even if not text/* Product: Tomcat 4 Version: 4.1.29 Platform: All OS/Version: All Status: NEW Severity: Critical Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] A JSP-Page (or Servlet) like % response.setContentType(application/pdf); % wurst results in the Content-Type-Header Content-Type: application/pdf;charset=ISO-8859-1 which is not allowed according to HTTP-RFCs. The charset may only be appended when the Content-Type is text/*. It causes bad behaviour with IE, that's this can be critical for some Servlets. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 12:55 --- Already fixed, can't find the commit message but this is close: http://marc.theaimsgroup.com/?l=tomcat-devm=106870694029743w=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23146] - Calling socket.setTcpNoDelay causes connector to disconnect
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23146. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23146 Calling socket.setTcpNoDelay causes connector to disconnect --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 12:57 --- Answer from Sun in relation to setTcpNoDelay failing is: This error is caused bya EINVAL return code from the setsockopt() system call.The most likely cause of this (considering that it happensonly sometimes) is that the socket has been shutdown or closedin some way, but Java (or Apache) thinks it is still open.Which version of Tomcat are you running, and how easy is it toreproduce this? As annoying as this is, this sounds reasonable. I can't say this isn't happening. So something could be opening sockets and closing them immediately. In which case the currently coyote connector handling, (especially = 4.1.29) looks like the correct behaviour. log the failed connection and ignore it. Could this be a port scanner or health check? I can't think of what would be doing that in our system. BTW I guess the catalina connector is still broken, because it doesn't catch the exception. But at least coyote connector handles it gracefully, and it isn't an indicator of bad health of the system. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 12:59 --- when can i expect the next tomcat 4.1 release? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 13:21 --- http://jakarta.apache.org/tomcat/faq/version.html#when - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs index.xml
yoavs 2003/11/25 05:56:10 Modified:xdocsindex.xml Log: Updated Tomcat 4.1 section which listed 4.1.27 as latest release. Revision ChangesPath 1.43 +2 -2 jakarta-tomcat-site/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs/index.xml,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- index.xml 30 Oct 2003 20:20:49 - 1.42 +++ index.xml 25 Nov 2003 13:56:10 - 1.43 @@ -93,8 +93,8 @@ implement the strongServlet 2.3/strong and strongJSP 1.2/strong specifications./p -pstrongTomcat 4.1.x/strong. Tomcat 4.1.27 Stable is the latest release. -Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and contains significant +pstrongTomcat 4.1.x/strong. Tomcat 4.1, whose latest stable release +is listed above, is a refactoring of Tomcat 4.0.x, and contains significant enhancements, including: ul liJMX based administration features/li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/docs bugreport.html index.html irc.html resources.html
yoavs 2003/11/25 05:57:22 Modified:docs bugreport.html index.html irc.html resources.html Log: Updated site Revision ChangesPath 1.17 +0 -2 jakarta-tomcat-site/docs/bugreport.html Index: bugreport.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/bugreport.html,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- bugreport.html20 Nov 2003 15:24:52 - 1.16 +++ bugreport.html25 Nov 2003 13:57:22 - 1.17 @@ -42,8 +42,6 @@ !-- LEFT SIDE NAVIGATION -- td width=20% valign=top nowrap=true -!-- to be removed after ApacheCon 2003 ends 20th of November 2003 -- -A HREF=http://apachecon.com/2003/US/index.html;img border=0 src=http://jakarta.apache.org/images/logos/ac2003-150.gif; alt=ApacheCon US 2003 -- Join US!//A !-- -- pstrongTomcat/strong/p 1.53 +2 -4 jakarta-tomcat-site/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/index.html,v retrieving revision 1.52 retrieving revision 1.53 diff -u -r1.52 -r1.53 --- index.html20 Nov 2003 15:24:52 - 1.52 +++ index.html25 Nov 2003 13:57:22 - 1.53 @@ -42,8 +42,6 @@ !-- LEFT SIDE NAVIGATION -- td width=20% valign=top nowrap=true -!-- to be removed after ApacheCon 2003 ends 20th of November 2003 -- -A HREF=http://apachecon.com/2003/US/index.html;img border=0 src=http://jakarta.apache.org/images/logos/ac2003-150.gif; alt=ApacheCon US 2003 -- Join US!//A !-- -- pstrongTomcat/strong/p @@ -252,8 +250,8 @@ Catalina) that is based on completely new architecture. The 4.x releases implement the strongServlet 2.3/strong and strongJSP 1.2/strong specifications./p -pstrongTomcat 4.1.x/strong. Tomcat 4.1.27 Stable is the latest release. -Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and contains significant +pstrongTomcat 4.1.x/strong. Tomcat 4.1, whose latest stable release +is listed above, is a refactoring of Tomcat 4.0.x, and contains significant enhancements, including: ul liJMX based administration features/li 1.18 +0 -2 jakarta-tomcat-site/docs/irc.html Index: irc.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/irc.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- irc.html 20 Nov 2003 15:24:52 - 1.17 +++ irc.html 25 Nov 2003 13:57:22 - 1.18 @@ -42,8 +42,6 @@ !-- LEFT SIDE NAVIGATION -- td width=20% valign=top nowrap=true -!-- to be removed after ApacheCon 2003 ends 20th of November 2003 -- -A HREF=http://apachecon.com/2003/US/index.html;img border=0 src=http://jakarta.apache.org/images/logos/ac2003-150.gif; alt=ApacheCon US 2003 -- Join US!//A !-- -- pstrongTomcat/strong/p 1.21 +0 -2 jakarta-tomcat-site/docs/resources.html Index: resources.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/resources.html,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- resources.html20 Nov 2003 15:24:52 - 1.20 +++ resources.html25 Nov 2003 13:57:22 - 1.21 @@ -42,8 +42,6 @@ !-- LEFT SIDE NAVIGATION -- td width=20% valign=top nowrap=true -!-- to be removed after ApacheCon 2003 ends 20th of November 2003 -- -A HREF=http://apachecon.com/2003/US/index.html;img border=0 src=http://jakarta.apache.org/images/logos/ac2003-150.gif; alt=ApacheCon US 2003 -- Join US!//A !-- -- pstrongTomcat/strong/p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 RELEASE-NOTES
remm2003/11/25 06:05:17 Modified:.RELEASE-NOTES Log: - Release notes update. Revision ChangesPath 1.9 +21 -17jakarta-tomcat-5/RELEASE-NOTES Index: RELEASE-NOTES === RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- RELEASE-NOTES 8 Sep 2003 13:49:23 - 1.8 +++ RELEASE-NOTES 25 Nov 2003 14:05:17 - 1.9 @@ -16,7 +16,7 @@ * Tomcat 5.0 and XML Parsers * Web application reloading and static fields in shared libraries * JAVAC leaking memory -* Linux and Sun JDK 1.2.x - 1.3.x +* Tomcat on Linux * Enabling SSI and CGI Support * Security manager URLs * Symlinking static resources @@ -54,9 +54,10 @@ for use by web applications (by placing them in common/lib or shared/lib): * ant.jar (Apache Ant) * commons-collections.jar (Commons Collections 2.1) -* commons-dbcp.jar (Commons DBCP 1.0) +* commons-dbcp.jar (Commons DBCP 1.1) * commons-el.jar (Commons Expression Language 1.0) -* commons-pool.jar (Commons Pool 1.0) +* commons-logging-api.jar (Commons Logging API 1.0.3) +* commons-pool.jar (Commons Pool 1.1) * jasper-compiler.jar (Jasper 2 Compiler) * jasper-runtime.jar (Jasper 2 Runtime) * jmx.jar (Sun JMX RI 1.2) @@ -115,21 +116,24 @@ Note: This issue has been fixed in Sun JDK 1.4.x. -Linux and Sun JDK 1.2.x - 1.3.x: +--- +Tomcat on Linux: +--- -Virtual machine crashes may be experienced when using certain combinations of -kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were +Virtual machine crashes can be experienced when using certain combinations of +kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were reported to occur mostly on startup. Sun JDK 1.4 does not exhibit the problems, and neither does IBM JDK for Linux. -The problems can be fixed by reducing the default stack size. From a bash shell, -use ulimit -s 2048; use limit stacksize 2048 for tcsh. +The problems can be fixed by reducing the default stack size. At bash shell, +do ulimit -s 2048; use limit stacksize 2048 for tcsh. GLIBC 2.2 / Linux 2.4 users should also define an environment variable: export LD_ASSUME_KERNEL=2.2.5 +Additionally, Redhat Linux 9.0 users should use the same setting, to avoid +stability problems. + Enabling SSI and CGI Support: @@ -148,8 +152,8 @@ %CATALINA_HOME%\server\lib\servlets-ssi.jar. * in %CATALINA_HOME%\conf\web.xml, uncomment the servlet declarations starting on lines 226 and 250, as well as the associated servlet mappings - on lines 276 and 294. Alternately, these servlet declarations and mappings can - be added to your web application deployment descriptor. + on lines 276 and 294. Alternately, these servlet declarations and mappings + can be added to your web application deployment descriptor. To enable CGI and SSI on Unix: * rename the file $CATALINA_HOME/server/lib/servlets-cgi.renametojar to @@ -158,8 +162,8 @@ $CATALINA_HOME/server/lib/servlets-ssi.jar. * in $CATALINA_HOME/conf/web.xml, uncomment the servlet declarations starting on lines 226 and 250, as well as the associated servlet mappings - on lines 276 and 294. Alternately, these servlet declarations and mappings can - be added to your web application deployment descriptor. + on lines 276 and 294. Alternately, these servlet declarations and mappings + can be added to your web application deployment descriptor. - @@ -181,8 +185,8 @@ Symlinking static resources: --- -By default, Unix symlinks will not work when used in a web application to link resources -located outside the web application root directory. +By default, Unix symlinks will not work when used in a web application to link +resources located outside the web application root directory. This behavior is optional, and the allowLinking flag may be used to disable the check. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 tomcat.nsi
remm2003/11/25 06:16:53 Modified:.tomcat.nsi Log: - Include the balancer webapp. Revision ChangesPath 1.38 +3 -1 jakarta-tomcat-5/tomcat.nsi Index: tomcat.nsi === RCS file: /home/cvs/jakarta-tomcat-5/tomcat.nsi,v retrieving revision 1.37 retrieving revision 1.38 diff -u -r1.37 -r1.38 --- tomcat.nsi5 Nov 2003 11:40:04 - 1.37 +++ tomcat.nsi25 Nov 2003 14:16:52 - 1.38 @@ -122,6 +122,7 @@ File /r work File /r temp SetOutPath $INSTDIR\webapps + File /r webapps\balancer File /r webapps\ROOT !insertmacro MUI_INSTALLOPTIONS_READ $2 jvm.ini Field 2 State @@ -487,6 +488,7 @@ RMDir /r $INSTDIR\shared RMDir $INSTDIR\logs RMDir /r $INSTDIR\server + RMDir /r $INSTDIR\webapps\balancer RMDir /r $INSTDIR\webapps\ROOT RMDir /r $INSTDIR\webapps\tomcat-docs RMDir /r $INSTDIR\webapps\servlets-examples - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[site] Metrics
Hi, I'd like to run some metrics (JDepend, CheckStyle) on the tomcat 5 source code and publish them on the web site. Does anyone think this is a bad idea? Since tomcat doesn't use Maven(*), and we don't have targets for these checks in our ant builds, I can do it manually on my local machine. I just wanted to make sure no one had an issue with publishing them. I think it's a good, transparent move. (*) = I'd like to use Maven ;) I even went as far as trying to write a maven POM for Tomcat 4.1 but the build was too complicated for my Maven skills at the time. Any Maven gurus out there are welcome to try... Yoav Shapira Millennium ChemInformatics 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 24972] New: - Some *.sh scripts in tar not executable.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972 Some *.sh scripts in tar not executable. Summary: Some *.sh scripts in tar not executable. Product: Tomcat 5 Version: 5.0.14 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Native:Packaging AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In my opinion, the *.sh scripts in jakarta-tomcat-5.0.14.tar.gz should all have the executalbe bit set, consistently, but not all do: $ tar tvzf jakarta-tomcat-5.0.14.tar.gz '*.sh' | perl -wane 'print $F[0], , $F[5], \n' -rwxr-xr-x jakarta-tomcat-5.0.14/bin/digest.sh -rwxr-xr-x jakarta-tomcat-5.0.14/bin/startup.sh -rwxr-xr-x jakarta-tomcat-5.0.14/bin/tool-wrapper.sh -rwxr-xr-x jakarta-tomcat-5.0.14/bin/catalina.sh -rwxr-xr-x jakarta-tomcat-5.0.14/bin/shutdown.sh -rwxr-xr-x jakarta-tomcat-5.0.14/bin/setclasspath.sh -rw-r--r-- jakarta-tomcat-5.0.14/bin/tool-wrapper-using-launcher.sh -rw-r--r-- jakarta-tomcat-5.0.14/bin/shutdown-using-launcher.sh -rw-r--r-- jakarta-tomcat-5.0.14/bin/startup-using-launcher.sh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [site] Metrics
Shapira, Yoav wrote: Hi, I'd like to run some metrics (JDepend, CheckStyle) on the tomcat 5 source code and publish them on the web site. Does anyone think this is a bad idea? Yes, me. Being too strict with coding styles is IMO bad, esp since it does not reflect the code quality of developers (ex: Costin writes efficient code). Plus it would be finger pointing at the worst offenders (ex: probably still Costin ;-) ). JDepend looks like some barely useable statistics (for simple components, it could be useful, but here it seems doubtful). Post the results if they are actually useful :) Since tomcat doesn't use Maven(*), and we don't have targets for these checks in our ant builds, I can do it manually on my local machine. I just wanted to make sure no one had an issue with publishing them. I think it's a good, transparent move. (*) = I'd like to use Maven ;) I even went as far as trying to write a maven POM for Tomcat 4.1 but the build was too complicated for my Maven skills at the time. Any Maven gurus out there are welcome to try... I'm probably not a big Maven fan. The current build is still a mess, but works better than with TC 4.1. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24968] - RELEASE-NOTES states wrong version of commons-dbcp
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24968 RELEASE-NOTES states wrong version of commons-dbcp [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 24972] - Some *.sh scripts in tar not executable.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972 Some *.sh scripts in tar not executable. [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 24972] - Some *.sh scripts in tar not executable.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24972 Some *.sh scripts in tar not executable. --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 14:43 --- Come to think of it, setclasspath.sh should probably not be marked executable, as it needs to be sourced in. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.xml RELEASE-NOTES
remm2003/11/25 06:57:59
Modified:.build.xml RELEASE-NOTES
Log:
- Small fixes.
Revision ChangesPath
1.171 +6 -0 jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -r1.170 -r1.171
--- build.xml 20 Nov 2003 22:42:14 - 1.170
+++ build.xml 25 Nov 2003 14:57:58 - 1.171
@@ -1427,6 +1427,9 @@
include name=bin/startup.sh /
include name=bin/shutdown.sh /
include name=bin/tool-wrapper.sh /
+include name=bin/tool-wrapper-using-launcher.sh /
+include name=bin/shutdown-using-launcher.sh /
+include name=bin/startup-using-launcher.sh /
/tarfileset
tarfileset dir=${tomcat.dist} mode=600 prefix=${final.name}
include name=conf/** /
@@ -1453,6 +1456,9 @@
exclude name=bin/startup.sh /
exclude name=bin/shutdown.sh /
exclude name=bin/tool-wrapper.sh /
+exclude name=bin/tool-wrapper-using-launcher.sh /
+exclude name=bin/shutdown-using-launcher.sh /
+exclude name=bin/startup-using-launcher.sh /
exclude name=conf/** /
exclude name=src/** /
/tarfileset
1.10 +3 -1 jakarta-tomcat-5/RELEASE-NOTES
Index: RELEASE-NOTES
===
RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- RELEASE-NOTES 25 Nov 2003 14:05:17 - 1.9
+++ RELEASE-NOTES 25 Nov 2003 14:57:59 - 1.10
@@ -86,6 +86,8 @@
you may replace the xercesImpl.jar file in common/endorsed with another
XML parser, as long as it is compatible with the JAXP 1.2 APIs.
+Xerces 2.5.0 is included.
+
---
Web application reloading and static fields in shared libraries:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
remm2003/11/25 06:58:16 Modified:webapps/docs changelog.xml Log: - Changelog update for 5.0.15. Revision ChangesPath 1.29 +74 -12jakarta-tomcat-catalina/webapps/docs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- changelog.xml 18 Nov 2003 20:38:29 - 1.28 +++ changelog.xml 25 Nov 2003 14:58:16 - 1.29 @@ -50,7 +50,7 @@ removed only on destroy, rather than on stop (remm) /update fix - bug9723/bug: Avoid unneccessray calls to RequestUtil.filter, + bug9723/bug: Avoid unnecessary calls to RequestUtil.filter, submitted by Arvind Srinivasan (amyroh) /fix fix @@ -66,7 +66,7 @@ usual / to conversion for the path) (remm) /fix update - All the properties definied in catalina.properties will now be set as + All the properties defined in catalina.properties will now be set as system properties (remm) /update update @@ -87,12 +87,37 @@ submitted by Mark Thomas (remm) /fix fix - bug24368/bug: Fix unhandled exceptionm submitted by Mark Thomas + bug24368/bug: Fix unhandled exception submitted by Mark Thomas (remm) /fix fix bug23764/bug: fix SSO logout (remm) /fix + fix + bug24829/bug: The command is the last parameter, not the first one + (remm) + /fix + fix + bug24832/bug: Merge code from JDBC realm, fixing the valve after + a restart of the database, submitted by submitted by Peter Rossbach + (remm) + /fix + update + bug23881/bug: SSO in embedded Tomcat, submitted by Brian Stansberry + (remm) + /update + update + When calling ServletContext.log, append the application's name so + we know from which application the log is coming (jfarcand) + /update + fix + Don't throw an ISE if Session.getLastModified is called while the + session is expiring, submitted by Brian Stansberry (remm) + /fix + fix + bug9077/bug: When a session timeouts, it won't logout of all webapps, + submitted by Brian Stansberry (remm) + /fix /changelog @@ -144,6 +169,25 @@ Add maxPostSize support for client cert, to allow limiting the size of the buffered data (billbarker, remm) /update + fix + Throw exception if keyAlias does not identify key entry in connector's + key store, to prevent infinite loop on + org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket (luehe) + /fix + fix + The KeyStore implementation (JKS) of the SUN provider converts + alias names to lower case, so we need to do the same (luehe) + /fix + fix + Fix character encoding for URL parameters: char decoding should only + occur after %xx decoding (remm) + /fix + fix + Fixes to remote address and host resolution through JMX (amyroh) + /fix + update + Add getters to the thread pool and HTTP connector (amyroh) + /update /changelog @@ -158,21 +202,21 @@ Matthias Ernst /fix update - Concatenate text strings of adjecent TemplateText nodes, which may + Concatenate text strings of adjacent TemplateText nodes, which may reduce code size and improve performance (kinman) /update fix bug10903/bug: Generate errors for unbalanced end tags (kinman) /fix docs - Add some javacdocs in EL related classes (kinman) + Add some javadocs in EL related classes (kinman) /docs fix Use ISO-8859-1 as the default encoding for lt;jsp:paramgt; since it is the default encoding for the request object (kinman) /fix update - A smal performance improvement: instantiate the bean object with its + A small performance improvement: instantiate the bean object with its constructor, if class attribute is specified in usebean, instead of going thru java.beans.Beans.instantiate() (kinman) /update @@ -191,6 +235,17 @@ docs Fix JSPC classpath in the docs (remm) /docs + fix + bug24904/bug: Nested custom tag causes bogus compilation errors + (kinman) + /fix + fix + bug24779/bug: Jasper fails to compile a valid JSP document + (xml syntax) when an EL string in template text contains a [] (kinman) + /fix + fix + bug24957/bug: Operators are mis-treated as
Re: ETA for Tomcat 5.0 Stable?
J2EE 1.4 has been released! As I understand (from personal use as well as that from lurking here), Tomcat 5.0 should be ready to be tagged any day as 5.0.15 and to achieve a stable rating. -- Jess Holle Jess Holle wrote: Remy Maucherat wrote: Jess Holle wrote: Remy Maucherat wrote: Jess Holle wrote: Now that J2EE 1.4 is going final this week, what is the ETA for a stable Tomcat 5.0.x release? It was my understanding that some Tomcat 5.0.x releases *might* have been considered stable, but this label was not considered since J2EE 1.4 was not yet final. We did fix bugs since, so that means the initial 5.0.x should be a lot more polished than previous .0.0 Tomcat releases. So where are we at now? Is 5.0.14 likely to be considered stable once J2EE 1.4 is? Or is a 5.0.15 coming down the pipe shortly? I see no specs here: http://www.jcp.org/en/jsr/detail?id=151 No specs = no 5.0.15. Understood. I'm by no means saying the Tomcat crew is not on the ball! Rather the press statements by Sun, etc, are that all this stuff is going final this week. The J2EE 1.4 was approved by vote as a final spec and Sun is supposed to releasing the spec itself and a new SunONE version supporting it as well -- both this week. The rumors say today, so if it's early enough for me (I'm in Europe) I'll tag Tomcat CVS at the same time. Otherwise, I'll tag it tomorrow. As for uploading the 5.0.15 build, it will likely happen tomorrow. Counting the vote, we're looking at the end of the week if there are no problems. Unless someone is blowing smoke here, I am thus assuming that 5.0.14 or a quick 5.0.15 will be up for a stable vote shortly *after* that occurs. I'm just trying to get an understanding as to whether this assumption is presumptuous -- and how things are likely to play out at that point. Specifically, I'm trying to determine how quickly/agressively to test Tomcat 5.0.x and whether 5.0.14 is a good target for this activity. With the exception of the charset issue, TC 5.0.14 seems like a decent build. Or you can get a nightly build, since the last one will be mostly equivalent to 5.0.15. Thanks for the info. That's exactly what I wanted to hear. -- Jess Holle - 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: [site] Metrics
Howdy, Yes, me. Being too strict with coding styles is IMO bad, esp since it does not reflect the code quality of developers (ex: Costin writes efficient code). Plus it would be finger pointing at the worst offenders (ex: probably still Costin ;-) ). I understand, and partially agree. Being too strict with coding styles is bad. Publishing metrics does not: - Force anyone to code in any style - Point fingers at anyone (the author names are not visible, the source code is not linked) What it does do is: - Make our project seem a bit more mature and open - Give us a handy reference for what to improve as the code base matures What I would probably do is run the metrics locally and put them under some URL on my account at apache.org, and let you know. We can see if they're useful at all at that point without publishing them to the whole world. 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 24976] New: - -Dcatalina.base=... does not work, but export CATALINA_BASE=... does
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24976. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24976 -Dcatalina.base=... does not work, but export CATALINA_BASE=... does Summary: -Dcatalina.base=... does not work, but export CATALINA_BASE=... does Product: Tomcat 5 Version: 5.0.14 Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Native:Integration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RUNNING.txt tells me to .../bin/startup.sh -Dcatalina.base=... but that does not work for me. Tomcat ignores the Catalina-base I'm trying to tell it, and starts with Catalina base = Catalina home instead. However, doing CATALINA_BASE=... export CATALINA_BASE .../bin/startup.sh works as intended. I suggest fixing the documentation in RUNNING.txt. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenti cator SingleSignOnEntry.java AuthenticatorBase.java BasicAuthenticator.java DigestAuthenticator.java FormAuthenticator.java NonLoginAuthenticator.java SSLAut
Nelson, Luke wrote: I tested it and it didn't throw the exception indicated earlier in this thread. I would rather this part of the patch be replaced with something more robust. There really isn't a need to test for the timeout as we should be able to know how the session expired by the session itself providing that information. Can you please double check, with Tomcat 5, that listeners are properly called when the session expire? This is an are where we are frequently regressing I don't have time now to test the patch (will take a look latter today) -- Jeanfrancois Luke -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 1:49 PM To: Tomcat Developers List Subject: Re: cvs commit: jakarta-tomcat- catalina/catalina/src/share/org/apache/catalina/authenti cator SingleSignOnEntry.java AuthenticatorBase.java BasicAuthenticator.java DigestAuthenticator.java FormAuthenticator.java NonLoginAuthenticator.java SSLAut Nelson, Luke wrote: Brian, I believe I just fixed those issues. See the latest patch to 9077. Did you actually test it ? Your patch calls getLastModified, does this really work if the session *did* timeout (and as such is no longer valid) ? 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.0.15] Test build available
5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.15] Test build available
Do you know when the 3.3.2 version will be available? tnx for any help... cya, GilsoN MeloTechnical Support EngineerSupport:55 11 5505-4066Fax:55 11 5505-4041AIM:gilsonsmeloNovell, Inc., the leading provider of information solutions. [EMAIL PROTECTED] 11/25 2:30 PM 5.0.15 is available for testing. Please be extra careful about regressions.If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that.http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ Rémy-To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:Gilson Melo TEL;WORK:55-11-3345-3976 ORG:;Technical Support - Brazil TEL;PREF;FAX:55-11-5505-4041 EMAIL;WORK;PREF;NGW:[EMAIL PROTECTED] N:Melo;Gilson TITLE:Technical Support Engineer ADR;DOM;WORK;PARCEL;POSTAL:;SAO:Brazil,Sao Paulo:Avenida Das Nacoes Unidas LABEL;DOM;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Gilson Melo=0A= SAO:Brazil,Sao Paulo:Avenida Das Nacoes Unidas END:VCARD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0.15] Test build available
Hi, Looks great ;) I've just tested the examples, admin, manager, balancer webapps, assorted links, and my own webapps which have Cactus tests. Everything worked fine. I should add a display-name to balancer's web.xml at some point. Yoav Shapira Millennium ChemInformatics -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 11:30 AM To: Tomcat Developers List Subject: [5.0.15] Test build available 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ Rémy - 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]
Re: Tomcat 3.3.2 release question - was RE: [5.0.15] Test build available
Unfortunately Tomcat 3.3.2 suffers from a release manager who can't seem to get out of an overworked state in his day job. I still intend to do a 3.3.2 release when I can find the time, but it is hard to predict when that will be given that my day job necessarily takes priority. Cheers, Larry P.S. Other than some changes needed due to new behavior in org.apache.tomcat.util.http.Parameter, there would not be any significant code differences between a released version and what is in CVS. I'll try to make those changes fairly soon, maybe over Thanksgiving. -Original Message- From: Gilson Melo [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: Re: [5.0.15] Test build available Do you know when the 3.3.2 version will be available? tnx for any help... cya, GilsoN Melo Technical Support Engineer Support: 55 11 5505-4066 Fax: 55 11 5505-4041 AIM: gilsonsmelo Novell, Inc., the leading provider of information solutions. [EMAIL PROTECTED] 11/25 2:30 PM 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* --- Additional Comments From [EMAIL PROTECTED] 2003-11-25 17:58 --- OK, i tried ... Well, can you point me at the code/class which needs a fix? I would have downgrade Tomcat, but i'd like keep 4.1.29 and patch it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime PerThreadTagHandlerPool.java
luehe 2003/11/25 10:05:06
Modified:jasper2/src/share/org/apache/jasper/runtime
PerThreadTagHandlerPool.java
Log:
General cleanup (for instance, perThread.get() was always returning null)
Revision ChangesPath
1.4 +46 -61
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PerThreadTagHandlerPool.java
Index: PerThreadTagHandlerPool.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PerThreadTagHandlerPool.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PerThreadTagHandlerPool.java 2 Sep 2003 21:39:59 - 1.3
+++ PerThreadTagHandlerPool.java 25 Nov 2003 18:05:06 - 1.4
@@ -63,27 +63,28 @@
import java.util.Enumeration;
import java.util.Hashtable;
+import java.util.Vector;
-import javax.servlet.Servlet;
+import javax.servlet.ServletConfig;
import javax.servlet.jsp.JspException;
import javax.servlet.jsp.tagext.Tag;
+import org.apache.jasper.Constants;
+
/**
- * Pool of tag handlers that can be reused.
- * Experimental: use thread local.
+ * Thread-local based pool of tag handlers that can be reused.
*
* @author Jan Luehe
* @author Costin Manolache
*/
public class PerThreadTagHandlerPool extends TagHandlerPool {
-public static int MAX_SIZE=100;
+private int maxSize;
+
+// For cleanup
+private Vector perThreadDataVector;
-private int maxSize=MAX_SIZE;
-private int initialSize=5;
-private ThreadLocal perThread=new ThreadLocal();
-// for cleanup
-private Hashtable threadData=new Hashtable();
+private ThreadLocal perThread;
private static class PerThreadData {
Tag handlers[];
@@ -95,26 +96,28 @@
*/
public PerThreadTagHandlerPool() {
super();
+perThreadDataVector = new Vector();
}
-protected void init(Servlet servlet) {
-String maxSizeS=TagHandlerPool.getOption(servlet.getServletConfig(),
OPTION_MAXSIZE, null);
-maxSize=Integer.parseInt(maxSizeS);
-if( maxSize 0 ) {
-maxSize=MAX_SIZE;
+protected void init(ServletConfig config) {
+maxSize = Constants.MAX_POOL_SIZE;
+String maxSizeS = getOption(config, OPTION_MAXSIZE, null);
+if (maxSizeS != null) {
+maxSize = Integer.parseInt(maxSizeS);
+if (maxSize 0) {
+maxSize = Constants.MAX_POOL_SIZE;
+}
}
-}
-/**
- * Constructs a tag handler pool with the given capacity.
- *
- * @param capacity Tag handler pool capacity
- * @deprecated
- */
-public PerThreadTagHandlerPool(int capacity) {
-this.maxSize = capacity;
- //this.handlers = new Tag[capacity];
- //this.current = -1;
+perThread = new ThreadLocal() {
+protected Object initialValue() {
+PerThreadData ptd = new PerThreadData();
+ptd.handlers = new Tag[maxSize];
+ptd.current = -1;
+perThreadDataVector.addElement(ptd);
+return ptd;
+}
+};
}
/**
@@ -128,8 +131,8 @@
* @throws JspException if a tag handler cannot be instantiated
*/
public Tag get(Class handlerClass) throws JspException {
-PerThreadData ptd=(PerThreadData)perThread.get();
-if( ptd!=null ptd.current =0 ) {
+PerThreadData ptd = (PerThreadData)perThread.get();
+if(ptd.current =0 ) {
return ptd.handlers[ptd.current--];
} else {
try {
@@ -149,44 +152,26 @@
*/
public void reuse(Tag handler) {
PerThreadData ptd=(PerThreadData)perThread.get();
-
-if( ptd==null ) {
-ptd=new PerThreadData();
-ptd.handlers=new Tag[ initialSize ];
-ptd.current=0;
-threadData.put( ptd, ptd );
-}
-
if (ptd.current (ptd.handlers.length - 1)) {
ptd.handlers[++ptd.current] = handler;
-return;
-}
-
-// no more space
-if( ptd.handlers.length maxSize ) {
-// reallocate
-Tag newH[]=new Tag[ptd.handlers.length + initialSize];
-System.arraycopy(ptd.handlers, 0, newH, 0, ptd.handlers.length);
-ptd.handlers=newH;
-ptd.handlers[++ptd.current]=handler;
-return;
+} else {
+handler.release();
}
-
-//else
- handler.release();
}
/**
- * Calls the release() method of all available tag handlers in this tag
- * handler pool.
+ *
IIS with Tomcat
You guys are going to like that: I've set up IIS 6.0 that I have at home with tomcat 4.1.29 then using the same settings, same config files, same isapi dll, did the same thing at work with IIS 5 and tomcat 4.1.29 and it doesn't work. I look at the log files and they're similar until one point. Take a look: This is the one with IIS 6.0 [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1018)]: Using registry. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1020)]: Using log file C:\Program Files\Apache Group\Tomcat 4.1\logs\isapi.log. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1021)]: Using log level 0. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1022)]: Using extension uri /jakarta/isapi_redirect.dll. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1023)]: Using worker file C:\Program Files\Apache Group\Tomcat 4.1\conf\workers.properties. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1024)]: Using worker mount file C:\Program Files\Apache Group\Tomcat 4.1\conf\uriworkermap.properties. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1025)]: Using uri select 0. [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (1041)]: Ignoring worker mount file entry default.worker=worker2. [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (172)]: Into jk_uri_worker_map_t::uri_worker_map_alloc [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (375)]: Into jk_uri_worker_map_t::uri_worker_map_open [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (396)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 6 [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (345)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /examples=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (345)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /examples/=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (321)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /examples/=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (299)]: Into jk_uri_worker_map_t::uri_worker_map_open, suffix rule /.jsp=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (345)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /servlet=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (345)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /servlet/=worker2 was added [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (408)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 6 rules [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (422)]: jk_uri_worker_map_t::uri_worker_map_open, done [Mon Nov 24 21:20:07 2003] [jk_worker.c (88)]: Into wc_open [Mon Nov 24 21:20:07 2003] [jk_worker.c (222)]: Into build_worker_map, creating 1 workers [Mon Nov 24 21:20:07 2003] [jk_worker.c (228)]: build_worker_map, creating worker worker2 [Mon Nov 24 21:20:07 2003] [jk_worker.c (148)]: Into wc_create_worker [Mon Nov 24 21:20:07 2003] [jk_worker.c (162)]: wc_create_worker, about to create instance worker2 of ajp13 [Mon Nov 24 21:20:07 2003] [jk_ajp13_worker.c (108)]: Into ajp13_worker_factory [Mon Nov 24 21:20:07 2003] [jk_worker.c (171)]: wc_create_worker, about to validate and init worker2 [Mon Nov 24 21:20:07 2003] [jk_ajp_common.c (1343)]: Into jk_worker_t::validate [Mon Nov 24 21:20:07 2003] [jk_ajp_common.c (1364)]: In jk_worker_t::validate for worker worker2 contact is 127.0.0.1:8009 [Mon Nov 24 21:20:07 2003] [jk_ajp_common.c (1397)]: Into jk_worker_t::init [Mon Nov 24 21:20:07 2003] [jk_ajp_common.c (1421)]: In jk_worker_t::init, setting socket timeout to 0 [Mon Nov 24 21:20:07 2003] [jk_worker.c (187)]: wc_create_worker, done [Mon Nov 24 21:20:07 2003] [jk_worker.c (238)]: build_worker_map, removing old worker2 worker [Mon Nov 24 21:20:07 2003] [jk_worker.c (250)]: build_worker_map, done [Mon Nov 24 21:20:07 2003] [jk_worker.c (111)]: wc_open, done 1 [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (655)]: Detected IIS = 5.0 [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (696)]: HttpFilterProc started [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (759)]: In HttpFilterProc Virtual Host redirection of /localhost/examples/ [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI '/localhost/examples/' [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match [Mon Nov 24 21:20:07 2003] [jk_isapi_plugin.c (765)]: In HttpFilterProc test Default redirection of /examples/ [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI '/examples/' [Mon Nov 24 21:20:07 2003] [jk_uri_worker_map.c (491)]: jk_uri_worker_map_t::map_uri_to_worker, Found an exact match worker2 - /examples/ [Mon Nov
DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970
charset appended to content-type even if not text/*
--- Additional Comments From [EMAIL PROTECTED] 2003-11-25 18:16 ---
Here's the patch.
Index: Response.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java,v
retrieving revision 1.29
retrieving revision 1.31
diff -r1.29 -r1.31
157a158,161
/**
* Has the charset been explicitly set.
*/
protected boolean charsetSet = false;
323a328
charsetSet = false;
473c478,479
characterEncoding = charset;
---
characterEncoding = charset;
charsetSet=true;
545a552
charsetSet=true;
555,557c562,565
if (ret != null characterEncoding != null) {
ret += ;charset=;
ret += characterEncoding;
---
if (ret != null
characterEncoding != null
charsetSet) {
ret = ret + ;charset= + characterEncoding;
589a598
charsetSet = false;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs balancer-howto.xml
yoavs 2003/11/25 10:22:30 Added: webapps/docs balancer-howto.xml Log: Added initial version of balancer document. Revision ChangesPath 1.1 jakarta-tomcat-catalina/webapps/docs/balancer-howto.xml Index: balancer-howto.xml === ?xml version=1.0? !DOCTYPE document [ !ENTITY project SYSTEM project.xml ] document url=balancer-howto.html project; properties author email=[EMAIL PROTECTED]Yoav Shapira/author titleLoad Balancer HOW-TO/title /properties body section name=Overview p Tomcat 5.0.15 and later ships with a webapp named balancer. This is a simple implemention of a rules-based load balancer. It was not designed as a replacement for other load-balancing mechanisms used for high traffic environments. Rather, it is a simple, pure Java, easily extensible, and fast way to direct traffic among multiple servers. /p /section section name=Sample Configuration p The default balancer installation uses a single filter, BalancerFilter, mapped to all requests (url-pattern /*). The filter reads its rules from the location specified in the balancer deployment descriptor (web.xml file). The default rules are: ul liRedirect requests with News in the URL to www.cnn.com/li liRedirect requests with a parameter named paramName whose value is paramValue to www.yahoo.com./li liRedirect all other requests to jakarta.apache.org./li /ul Therefore, when you install tomcat, start it, and point your browser to http://localhost:8080/balancer, you will be redirected to http://jakarta.apache.org. If you point your browser to http://localhost:8080/balancer/News you will be redirected to http://www.cnn.com. The request for http://localhost:8080/balancer/BlahBlah?paramName=paramValue will be redirected to http://www.yahoo.com. /p /section section name=Balancer Rules p A iRule/i in the balancer system is a combination of a request matching criterion and a redirection URL for matching requests. Rules implement the org.apache.webapp.balancer.Rule interface. /p p The balancer distribution contains a number of useful rules. The framework is also designed for easy extensibility so that you can write your own rules quickly. Rules should be JavaBeans (public no-args constructor, public setter method setXXX for property xxx), as they are instantiated by Jakarta Commons Digester. Feel free to inquire on the tomcat-user mailist list regarding the availability of rules of the inclusion of your rules in the distribution. /p p Rules are assembled into RuleChains. Each BalancerFilter (or Servlet/JSP) refers to one RuleChain when making its redirection decisions. Not that you are not restricted to having one filter mapped to /*, as is the default configuration. You can configure as many filters as desired, using the full filter mapping possibilities defined in the Servlet Specification. Each filter will have its own RuleChain. /p /section section name=How it Works p Here is the flow of events in the balancer: ol liYou write a rules configuration file containing various rules and redirection locations./li liYou define the balancer filter in your web.xml, mapping it as desired (/* is a common use-case) and configuring it with your rules configuration file./li liThe server is started, initializing the filter./li liA request comes into the server. The filter consults its rule chain to determine where to redirect the request. Rules are consulted in the order in which they are defined in the rules configuration file. The first matching rule will stop the evaluation and cause the request to be redirected./li /ol /p /section /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs index.xml
yoavs 2003/11/25 10:24:09 Modified:webapps/docs index.xml Log: Added balancer Revision ChangesPath 1.12 +3 -0 jakarta-tomcat-catalina/webapps/docs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/index.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- index.xml 15 Oct 2003 01:57:59 - 1.11 +++ index.xml 25 Nov 2003 18:24:09 - 1.12 @@ -9,6 +9,7 @@ properties author email=[EMAIL PROTECTED]Craig R. McClanahan/author author email=[EMAIL PROTECTED]Remy Maucherat/author +author email=[EMAIL PROTECTED]Yoav Shapira/author titleDocumentation Index/title /properties @@ -91,6 +92,8 @@ Configuring the default servlet and customizing directory listings./li lia href=cluster-howto.htmlstrongTomcat Clustering/strong/a - Enable session replication in a Tomcat environment./li +lia href=balancer-howto.htmlstrongBalancer/strong/a - +Configuring, using, and extending the load balancer application./li /ol - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs developers.xml
yoavs 2003/11/25 10:24:51 Modified:webapps/docs developers.xml Log: Revision ChangesPath 1.4 +1 -1 jakarta-tomcat-catalina/webapps/docs/developers.xml Index: developers.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/developers.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- developers.xml22 Jun 2003 18:29:06 - 1.3 +++ developers.xml25 Nov 2003 18:24:51 - 1.4 @@ -42,7 +42,7 @@ liRemy Maucherat (remm): Catalina, Connectors, Docs, Release Manager/li liTim Funk (funkman): Catalina, Docs/li - liYoav Shapira (yoavs): Docs, JMX/li + liYoav Shapira (yoavs): Docs, JMX, Catalina, balancer/li /ul /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.15] Test build available
From: Remy Maucherat [EMAIL PROTECTED] 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ Rémy Hi Rémy, Would there be any harm in excluding the jk/native* directories from the src distribution? I think it would help avoid people from building the native connectors from this src archive. What happens frequently is that people build the native connectors from tomcat src distribution thinking that they are building the stable released versions. -Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs balancer-howto.xml
yoavs 2003/11/25 10:38:49 Modified:webapps/docs balancer-howto.xml Log: Updated Revision ChangesPath 1.2 +17 -5 jakarta-tomcat-catalina/webapps/docs/balancer-howto.xml Index: balancer-howto.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/balancer-howto.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- balancer-howto.xml25 Nov 2003 18:22:30 - 1.1 +++ balancer-howto.xml25 Nov 2003 18:38:49 - 1.2 @@ -23,7 +23,13 @@ environments. Rather, it is a simple, pure Java, easily extensible, and fast way to direct traffic among multiple servers. /p - +p +Although balancer ships with tomcat, it is not tomcat-specific and runs +on other containers without any modification. The balancer webapp +requires a Servlet Specification 2.3 or later container if you wish +to use a filter to redirect traffic. If you wish to redirect traffic +using a servlet, you may use any servlet container. +/p /section section name=Sample Configuration @@ -64,7 +70,7 @@ should be JavaBeans (public no-args constructor, public setter method setXXX for property xxx), as they are instantiated by Jakarta Commons Digester. Feel free -to inquire on the tomcat-user mailist list regarding +to inquire on the tomcat-user mailing list regarding the availability of rules of the inclusion of your rules in the distribution. /p @@ -72,8 +78,8 @@ p Rules are assembled into RuleChains. Each BalancerFilter (or Servlet/JSP) refers to one RuleChain when making its -redirection decisions. Not that you are not restricted -to having one filter mapped to /*, as is the default +redirection decisions. Note that you are not restricted +to having one filter mapped to /* as done in the sample configuration. You can configure as many filters as desired, using the full filter mapping possibilities defined in the Servlet Specification. Each filter will have @@ -83,7 +89,6 @@ section name=How it Works p -Here is the flow of events in the balancer: ol liYou write a rules configuration file containing various rules and redirection locations./li @@ -99,6 +104,13 @@ /ol /p +/section + +section name=Comments +p +Please direct questions, comments, suggestions, etc. to the +tomcat-user mailing list. Thank you. +/p /section /body - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.15] Test build available
OK I've ran: - Servlet 2.4 TCKS - JSP 2.0 TCKS with validation enabled/disabled, security enabled/disabled. I also tested admin with security enabled. They all passes. -- Jeanfrancois Remy Maucherat wrote: 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler JspDocumentParser.java
kinman 2003/11/25 10:51:47
Modified:jasper2/src/share/org/apache/jasper/compiler
JspDocumentParser.java
Log:
- In XML syntax, recognize \$ escape sequence in template text.
Revision ChangesPath
1.73 +11 -8
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java
Index: JspDocumentParser.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- JspDocumentParser.java24 Nov 2003 23:51:10 - 1.72
+++ JspDocumentParser.java25 Nov 2003 18:51:47 - 1.73
@@ -523,18 +523,21 @@
ttext.write(ch);
lastCh = ch;
}
+} else if (lastCh == '\\' ch == '$') {
+ttext.write('$');
+ch = 0; // Not start of EL anymore
} else {
-if ((lastCh == '$') (ch != '{')) {
-ttext.write('$');
+if (lastCh == '$' || lastCh == '\\') {
+ttext.write(lastCh);
}
-if (ch != '$') {
+if (ch != '$' ch != '\\') {
ttext.write(ch);
}
}
lastCh = ch;
}
-if (lastCh == '$') {
-ttext.write('$');
+if (lastCh == '$' || lastCh == '\\') {
+ttext.write(lastCh);
}
if (ttext.size() 0) {
new Node.TemplateText(ttext.toString(), startMark, current);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/conf server.xml
yoavs 2003/11/25 11:14:47 Modified:catalina/src/conf server.xml Log: Corrected typo and grammar error in XML validation warning. Revision ChangesPath 1.26 +1 -1 jakarta-tomcat-catalina/catalina/src/conf/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/server.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- server.xml7 Oct 2003 14:38:12 - 1.25 +++ server.xml25 Nov 2003 19:14:46 - 1.26 @@ -209,7 +209,7 @@ -- !-- Define the default virtual host - Note: XML Schema validationn will not works with Xerces 2.2. + Note: XML Schema validation will not work with Xerces 2.2. -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0.15] Test build available
Howdy, FYI, I just added a balancer how-to document that I think should ship with 5.0.15. I didn't want to tag it myself at this point. Yoav Shapira Millennium ChemInformatics -Original Message- From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 1:52 PM To: Tomcat Developers List Subject: Re: [5.0.15] Test build available OK I've ran: - Servlet 2.4 TCKS - JSP 2.0 TCKS with validation enabled/disabled, security enabled/disabled. I also tested admin with security enabled. They all passes. -- Jeanfrancois Remy Maucherat wrote: 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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] 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: Tomcat 3.3.2 release question - was RE: [5.0.15] Test build available
tnx for the information... if you get any news, please, let me know... cya, GilsoN Melo Technical Support Engineer Support: [EMAIL PROTECTED] 11/25/03 10:46 AM Unfortunately Tomcat 3.3.2 suffers from a release manager who can't seem to get out of an overworked state in his day job. I still intend to do a 3.3.2 release when I can find the time, but it is hard to predict when that will be given that my day job necessarily takes priority. Cheers, Larry P.S. Other than some changes needed due to new behavior in org.apache.tomcat.util.http.Parameter, there would not be any significant code differences between a released version and what is in CVS. I'll try to make those changes fairly soon, maybe over Thanksgiving. -Original Message- From: Gilson Melo [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: Re: [5.0.15] Test build available Do you know when the 3.3.2 version will be available? tnx for any help... cya, GilsoN Melo Technical Support Engineer Support: 55 11 5505-4066 Fax: 55 11 5505-4041 AIM: gilsonsmelo Novell, Inc., the leading provider of information solutions. [EMAIL PROTECTED] 11/25 2:30 PM 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tools for Installing/Configuring Tomcat 4.x on Mac OS 10.2.8 and for Migrating Tomcat 3.x web applications to Tomcat 4.x
Hello. Does anyone know of any software tools that manage the installation/configuration of Tomcat 4.x on Mac OS 10.2.8 and also the migration of Tomcat 3.x web applications(using JSP/Servlet technology) to Tomcat 4.x? Thanks. -Asad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.15] Test build available
Tomcat 5's tomcat.exe and tomcatw.exe do not work in the manner then used to in Tomcat 4.1.29. Can someone please point me to information on the changes? Or is the intent that tomcat.exe should work as it did in 4.1.29? [In which case, it clearly does not.] -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
IIS 5.0 and Tomcat 4.1.x
Has anyone setup the ISAPI plugin with IIS 5.0 and Tomcat 4.1.x??? If yes, could you e-mail me a copy of the ISAPI dll that you used? Maybe even worker, worker mount, and server.xml files..? Thanks a lot. _ Groove on the latest from the hot new rock groups! Get downloads, videos, and more here. http://special.msn.com/entertainment/wiredformusic.armx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0.15] Test build available
Howdy, Howdy, FYI, I just added a balancer how-to document that I think should ship with 5.0.15. I didn't want to tag it myself at this point. Too late ;-) I think we'll update the online docs if the release does actually happen. I'll settle for a jakarta.apache.org update after the release. I think we'll have a fairly quick 5.0.16 anyways after tens of thousands of people use 5.0.15 for a couple of weeks ;) 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: Tomcat 3.3.2 release question - was RE: [5.0.15] Test build available
Hello Larry, Thanks for your reply What i need is the new function that Tomcat 3.3.2 has that is secureCookie. This attribute guarantees that the user will only send the session cookie in a secure connection using SSL. Since my application runs on Tomcat 4, do you know if Tomcat 4 has this feature ? Gilson, thanks for the contact. Eduardo Campoy Technology Account Manager Novell, THE leading provider of net business solutions Tel - 55 11 3345-3938 Cel - 55 11 9232-7456 AIM - ecampoy sao MSN - [EMAIL PROTECTED] [EMAIL PROTECTED] 25/11/2003 15:46:31 Unfortunately Tomcat 3.3.2 suffers from a release manager who can't seem to get out of an overworked state in his day job. I still intend to do a 3.3.2 release when I can find the time, but it is hard to predict when that will be given that my day job necessarily takes priority. Cheers, Larry P.S. Other than some changes needed due to new behavior in org.apache.tomcat.util.http.Parameter, there would not be any significant code differences between a released version and what is in CVS. I'll try to make those changes fairly soon, maybe over Thanksgiving. -Original Message- From: Gilson Melo [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: Re: [5.0.15] Test build available Do you know when the 3.3.2 version will be available? tnx for any help... cya, GilsoN Melo Technical Support Engineer Support: 55 11 5505-4066 Fax: 55 11 5505-4041 AIM: gilsonsmelo Novell, Inc., the leading provider of information solutions. [EMAIL PROTECTED] 11/25 2:30 PM 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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]
Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 12:27 AM Subject: Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java [EMAIL PROTECTED] wrote: amyroh 2003/11/24 15:01:22 Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java util/java/org/apache/tomcat/util/net PoolTcpEndpoint.java Log: Add getters for all attributes defined in MBeanInfo so getAttribute calls suceed. Rectification: I'll integrate your patch, but it would be best to remove the fields which are duplicated with the thread pool MBean. Question... How are the attributes for these MBeans in j-t-c get generated? I don't see descriptor files. It seems if you have setters, the correspondent attributes get automatically added to MBeanInfo. And you get an error trying to getAttribute on the attribute which is included in MBeanInfo because it's missing getter methods. Thanks, Amy 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]
Re: [5.0.15] Test build available
Shapira, Yoav wrote: Howdy, Howdy, FYI, I just added a balancer how-to document that I think should ship with 5.0.15. I didn't want to tag it myself at this point. Too late ;-) I think we'll update the online docs if the release does actually happen. I'll settle for a jakarta.apache.org update after the release. I think we'll have a fairly quick 5.0.16 anyways after tens of thousands of people use 5.0.15 for a couple of weeks ;) I hope there won't be any urgent updates needed (and that any regression will be caught before the end of the week), given all the stuff that is in common with 4.1.x, or has been beta tested for a while. Rémy - 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 JspDocumentParser.java
kinman 2003/11/25 14:59:27
Modified:jasper2/src/share/org/apache/jasper/compiler
JspDocumentParser.java
Log:
- Make sure that white spaces in template texts around ![CDATA[...]]
are trimmed.
Revision ChangesPath
1.74 +9 -4
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java
Index: JspDocumentParser.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -r1.73 -r1.74
--- JspDocumentParser.java25 Nov 2003 18:51:47 - 1.73
+++ JspDocumentParser.java25 Nov 2003 22:59:27 - 1.74
@@ -615,6 +615,9 @@
* See org.xml.sax.ext.LexicalHandler.
*/
public void comment(char[] buf, int offset, int len) throws SAXException {
+
+processChars(); // Flush char buffer and remove white spaces
+
// ignore comments in the DTD
if (!inDTD) {
startMark =
@@ -630,6 +633,8 @@
* See org.xml.sax.ext.LexicalHandler.
*/
public void startCDATA() throws SAXException {
+
+processChars(); // Flush char buffer and remove white spaces
startMark =
new Mark(path, locator.getLineNumber(), locator.getColumnNumber());
}
@@ -638,7 +643,7 @@
* See org.xml.sax.ext.LexicalHandler.
*/
public void endCDATA() throws SAXException {
-// do nothing
+processChars(); // Flush char buffer and remove white spaces
}
/*
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/tester/web/golden JspDoc02.txt
kinman 2003/11/25 15:05:13 Modified:tester/web/golden JspDoc02.txt Log: - Update golden file to reflect changes in jasper regarding template text output in XML syntax. Sorry, Remy :) Revision ChangesPath 1.3 +0 -5 jakarta-tomcat-catalina/tester/web/golden/JspDoc02.txt Index: JspDoc02.txt === RCS file: /home/cvs/jakarta-tomcat-catalina/tester/web/golden/JspDoc02.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- JspDoc02.txt 25 Nov 2003 08:31:55 - 1.2 +++ JspDoc02.txt 25 Nov 2003 23:05:13 - 1.3 @@ -1,12 +1,7 @@ htmlheadtitleExample JSP in XML format/title/headbody This is the output of a simple JSP using XML format. br/divUse a jsp:scriptlet to loop from 1 to 10: /div1, 2, 3, 4, 5, 6, 7, 8, 9, 10 - - - brbr - - div align=left Use a jsp:expression to write something: foo/div - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 3.3.2 release question - was RE: [5.0.15] Testbuild available
I'm afraid I'm still ignorant in certain areas of Tomcat 4 configuration. I don't know what Tomcat 4 might have that is equivalent to this feature. I believe Tomcat 4 won't allow you to keep your session when going from HTTP to HTTPS and I assume it wouldn't expose the session if trying to do the reverse. I don't know if there are configuration options that affect this behavior. Cheers, Larry -Original Message- From: Eduardo Campoy [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 4:22 PM To: [EMAIL PROTECTED]; Larry Isaacs Cc: Edison Rodrigues; Fernando Freitas; Gilson Melo Subject: Re: Tomcat 3.3.2 release question - was RE: [5.0.15] Testbuild available Hello Larry, Thanks for your reply What i need is the new function that Tomcat 3.3.2 has that is secureCookie. This attribute guarantees that the user will only send the session cookie in a secure connection using SSL. Since my application runs on Tomcat 4, do you know if Tomcat 4 has this feature ? Gilson, thanks for the contact. Eduardo Campoy Technology Account Manager Novell, THE leading provider of net business solutions Tel - 55 11 3345-3938 Cel - 55 11 9232-7456 AIM - ecampoy sao MSN - [EMAIL PROTECTED] [EMAIL PROTECTED] 25/11/2003 15:46:31 Unfortunately Tomcat 3.3.2 suffers from a release manager who can't seem to get out of an overworked state in his day job. I still intend to do a 3.3.2 release when I can find the time, but it is hard to predict when that will be given that my day job necessarily takes priority. Cheers, Larry P.S. Other than some changes needed due to new behavior in org.apache.tomcat.util.http.Parameter, there would not be any significant code differences between a released version and what is in CVS. I'll try to make those changes fairly soon, maybe over Thanksgiving. -Original Message- From: Gilson Melo [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: Re: [5.0.15] Test build available Do you know when the 3.3.2 version will be available? tnx for any help... cya, GilsoN Melo Technical Support Engineer Support: 55 11 5505-4066 Fax: 55 11 5505-4041 AIM: gilsonsmelo Novell, Inc., the leading provider of information solutions. [EMAIL PROTECTED] 11/25 2:30 PM 5.0.15 is available for testing. Please be extra careful about regressions. If there are significant regressions, those will need to be fixed ASAP, and I'll release a new build shortly after that. http://www.apache.org/dist/jakarta/tomcat-5/v5.0.15-alpha/ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24996] New: - fdf reponse content type application/vdn.fdf
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24996 fdf reponse content type application/vdn.fdf Summary: fdf reponse content type application/vdn.fdf Product: Tomcat 5 Version: 5.0.14 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Servlet JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have an application that was built using 4.1.0. It has a content type of application/vnd.fdf which is a PDF forms filler. The JSP opens a pdf on the client and fills it with the text that I have sent down. When I moved this to our test server which is updated to 4.1.29, it changes from a PDF to a file download. I have also tried it on 5.0.14 and subsequently it is broken also. The only differences that I see are the forced charset. I have noticed that it does not show up on 4.1.0 but no matter what I do for the other versions, it always includes it. I have tried it on a windows based server as well as AIX 64 5.1. I have included a chuck of the JSP code and I also include RAW data captured across the port. --jsp-- %@ page language=java import=javax.naming.*, javax.sql.*,java.sql.*,java.util.*,com.lowagie.text.*,com.lowagie.text.pdf.* %% response.setHeader(Pragma, No-cache); response.setDateHeader(Expires, 0); response.setContentType(application/vnd.fdf); %%FDF-1.2 %âãÏÓ 1 0 obj /FDF /F(http://%=request.getServerName()%/RiskMgmt/pdfs/% =EELocationState.toLowerCase()%.pdf) /ID [7a0631678ed475f0898815f0a818cfa1bef7724317b311718e8675b677ef9b4e] /Fields[ /T(InsuranceCarrierFull)/V(%= InsCarrier_InsCarrierName+\n+InsCarrier_Address01+\n+InsCarrier_City+, +I nsCarrier_State+ +InsCarrier_zip+ (Ph - +InsCarrier_phone+) (Fx - +InsCarrier_fax+) %) /T(InsuranceCarrierName)/V(%= InsCarrier_InsCarrierName %) ] endobj trailer /Root 1 0 R %%EOF end jsp= --- RAW DATA --- jakarta-tomcat-5.0.14 Does not Work. ---Server to Client #1--- HTTP/1.1 200 OK Set-Cookie: JSESSIONID=AFCAE367736BB706108D34740CE678C2; Path=/ Pragma: No-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Type: application/vnd.fdf;charset=ISO-8859-1 Content-Length: 3298 Date: Tue, 25 Nov 2003 23:11:07 GMT Server: Apache-Coyote/1.1 Connection: close ---Server to Client #1--- 72 84 84 80 47 49 46 49 32 50 48 48 32 79 75 13 10 83 101 116 45 67 111 111 107 105 101 58 32 74 83 69 83 83 73 79 78 73 68 61 65 70 67 65 69 51 54 55 55 51 54 66 66 55 48 54 49 48 56 68 51 52 55 52 48 67 69 54 55 56 67 50 59 32 80 97 116 104 61 47 13 10 80 114 97 103 109 97 58 32 78 111 45 99 97 99 104 101 13 10 69 120 112 105 114 101 115 58 32 84 104 117 44 32 48 49 32 74 97 110 32 49 57 55 48 32 48 48 58 48 48 58 48 48 32 71 77 84 13 10 67 111 110 116 101 110 116 45 84 121 112 101 58 32 97 112 112 108 105 99 97 116 105 111 110 47 118 110 100 46 102 100 102 59 99 104 97 114 115 101 116 61 73 83 79 45 56 56 53 57 45 49 13 10 67 111 110 116 101 110 116 45 76 101 110 103 116 104 58 32 51 50 57 56 13 10 68 97 116 101 58 32 84 117 101 44 32 50 53 32 78 111 118 32 50 48 48 51 32 50 51 58 49 49 58 48 55 32 71 77 84 13 10 83 101 114 118 101 114 58 32 65 112 97 99 104 101 45 67 111 121 111 116 101 47 49 46 49 13 10 67 111 110 110 101 99 116 105 111 110 58 32 99 108 111 115 101 13 10 13 10 37 70 68 70 45 49 46 50 10 37 -30 -29 -49 -45 10 49 32 48 32 111 98 106 10 60 60 10 9 47 70 68 70 10 9 9 60 60 10 9 9 9 47 70 40 104 116 116 112 58 47 47 98 101 115 116 119 120 112 110 97 116 104 97 110 122 47 82 105 115 107 77 103 109 116 47 112 100 102 115 47 46 112 100 102 41 10 9 9 9 47 73 68 91 60 55 97 48 54 51 49 54 55 56 101 100 52 55 53 102 48 56 57 56 56 49 53 102 48 97 56 49 56 99 102 97 49 62 60 98 101 102 55 55 50 52 51 49 55 98 51 49 49 55 49 56 101 56 54 55 53 98 54 55 55 101 102 57 98 52 101 62 93 10 9 9 9 47 70 105 101 108 100 115 91 10 9 9 9 9 60 60 47 84 40 73 110 115 117 114 97 110 99 101 67 97 114 114 105 101 114 70 117 108 108 41 47 86 40 10 10 44 32 32 32 40 80 104 32 45 32 41 32 40 70 120 32 45 32 41 41 62 62 10 9 9 9 9 60 60 47 84 40 73 110 115 117 114 97 110 99 101 67 97 114 114 105 101 114 78 97 109 101 41 47 86 40 41 62 62 10 9 9 9 9 60 60 47 84 40 73 110 115 117 114 97 110 99 101 67 97 114 114 105 101 114 70 97 120 41 47 86 40 41 62 62 10 9 9 9 9 60 60 47 84 40 73 110 115 67 97 114 114 105 101 114 95 80 111 108
DO NOT REPLY [Bug 24996] - fdf reponse content type application/vdn.fdf
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24996 fdf reponse content type application/vdn.fdf [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-11-26 00:12 --- *** This bug has been marked as a duplicate of 24970 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24970 charset appended to content-type even if not text/* [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-11-26 00:12 --- *** Bug 24996 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24998] New: - Seem to experiencing problems with sessions with multiple connects through a proxy
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24998. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24998 Seem to experiencing problems with sessions with multiple connects through a proxy Summary: Seem to experiencing problems with sessions with multiple connects through a proxy Product: Tomcat 3 Version: 3.3 Final Platform: All OS/Version: Other Status: UNCONFIRMED Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, we have created intranet solutions for a couple of the projects that we are working on, however we are finding that when users connect to our sites through a proxy (namly ISA) the sessions are getting confused between the users. Each user is seeing the results of the other user. We have generated a random parameter for each request to place on the url to try to counter these proxy issues, however the issue seems to be in tomcat's (or possibily Apache's as we are using a Apache/Tomcat worker setup) session indentification. A problem that has emerged resently from this is SOME (not all) of a session's objects (JAVA Beans) are been invalidated, while others are not. An example of this is our DBManager which uses a predefined and created MaxID class.. This maxID class has been invalidated, however the DBManager was not. These are both declared on every page by use of a header.jsp which is included. This may not be a bug, although I have been looking at the problem on and off for a month and can't seem to find any information on the issue, or resolve the origin of issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs proxy-howto.xml
glenn 2003/11/25 19:42:37 Modified:webapps/tomcat-docs proxy-howto.xml Log: Replace references to mod_webapp with mod_jk, add Apache 2 mod_proxy section Revision ChangesPath 1.4 +13 -7 jakarta-tomcat-4.0/webapps/tomcat-docs/proxy-howto.xml Index: proxy-howto.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/proxy-howto.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- proxy-howto.xml 12 Jan 2003 17:26:46 - 1.3 +++ proxy-howto.xml 26 Nov 2003 03:42:37 - 1.4 @@ -19,7 +19,7 @@ pUsing standard configurations of Tomcat, web applications can ask for the server name and port number to which the request was directed for processing. When Tomcat is running standalone with the -a href=config/http11.htmlHTTP/1.1 Connector/a, it will generally +a href=config/coyote.htmlCoyote HTTP/1.1 Connector/a, it will generally report the server name specified in the request, and the port number on which the strongConnector/strong is listening. The two servlet API calls of interest, for this purpose, are:/p @@ -47,7 +47,7 @@ pApache 1.3 supports an optional module (codemod_proxy/code) that configures the web server to act as a proxy server. This can be used to forward requests for a particular web application to a Tomcat 4 instance, -without having to configure a web connector such as codemod_webapp/code. +without having to configure a web connector such as codemod_jk/code. To accomplish this, you need to perform the following tasks:/p ol liConfigure your copy of Apache so that it includes the @@ -116,12 +116,18 @@ pWhen requests are proxied in this manner, strongall/strong requests for the configured web applications will be processed by Tomcat (including -requests for static content). You will often be able to improve performance -by using the codemod_webapp/code web connector instead, which -automatically configures itself to have Apache handle static content that is -not processed by filters or security constraints defined within the web -application's deployment descriptor (code/WEB-INF/web.xml/code)./p +requests for static content). You can improve performance by using the +codemod_jk/code web connector instead of codemod_proxy/code. +codemod_jk/code can be configured so that the web server serves static +content that is not processed by filters or security constraints defined +within the web application's deployment descriptor +(code/WEB-INF/web.xml/code)./p +/section + +section name=Apache 2.0 Proxy Support +The same instructions hold true as for 1.3. (Except in Apache 2.0, +you may omit codeAddModule mod_proxy.c/code) /section /body - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs proxy-howto.xml
glenn 2003/11/25 19:43:31 Modified:webapps/docs proxy-howto.xml Log: Add back in reference to using mod_jk for serving static content Revision ChangesPath 1.5 +6 -2 jakarta-tomcat-catalina/webapps/docs/proxy-howto.xml Index: proxy-howto.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/proxy-howto.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- proxy-howto.xml 19 Jun 2003 21:37:15 - 1.4 +++ proxy-howto.xml 26 Nov 2003 03:43:31 - 1.5 @@ -116,8 +116,12 @@ pWhen requests are proxied in this manner, strongall/strong requests for the configured web applications will be processed by Tomcat (including -requests for static content). -/p +requests for static content). You can improve performance by using the +codemod_jk/code web connector instead of codemod_proxy/code. +codemod_jk/code can be configured so that the web server serves static +content that is not processed by filters or security constraints defined +within the web application's deployment descriptor +(code/WEB-INF/web.xml/code)./p /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23881] - SingleSignOn and FormAuthenticator in embedded tomcat
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23881. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23881 SingleSignOn and FormAuthenticator in embedded tomcat --- Additional Comments From [EMAIL PROTECTED] 2003-11-26 04:53 --- Created an attachment (id=9288) Port of the TC5 patch to TC 4.1; includes related fix to 9077 and 10040 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
