dev@tomcat.apache.org
Hi Mark, I know that RFC 3986 is the successor from RFC 1738, but the query parameter definition (3.4 Page 23) isn't usefull. The HttpUtils.parseQueryString() definition is good, but not a complete BNF. The wikipedia definition http://en.wikipedia.org/wiki/Query_string is much better. OK, I also think that double "&&" is an uncorrect query part, but at my case, some site grabber's use those query strings to made trouble :-( Peter Am 29.02.2008 um 19:43 schrieb Mark Thomas: Peter Rossbach wrote: Hi, I see the following warning with following request "http:// localhost:8080/snoopy/snoopy.jsp?hello=xxx&&world=yyy" Tomct 5.5.26 == 29.02.2008 13:49:29 org.apache.tomcat.util.http.Parameters processParameters WARNUNG: Parameters: Invalid chunk ignored. === Both parameter hello and world has the correct values, but every request logs a warning. At high traffic sites this anno user fault made admins really unhappy. At RFC 1738 only the following BNF are reference: That RFC is out of date. You want RFC 3986. Neither RFC actually defines how a parameter string should be formatted. I did quite a bit of googling but the best reference I found was the JavaDoc in the servlet spec for HttpUtils.parseQueryString() which suggests your URL above does indeed have a suspect query string because of the double &&. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42037] User principal not always set correctly
https://issues.apache.org/bugzilla/show_bug.cgi?id=42037 Mark Thomas <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||WONTFIX --- Comment #9 from Mark Thomas <[EMAIL PROTECTED]> 2008-03-01 09:49:05 --- I am marking this as WONTFIX since: - there are no obvious code paths that could explain this - no reasoning has been provided for why the patch works and I can't see one - there has been no response to the request for further info for many months I suspect tile and/or the app is doing something odd. If you, or anyone else, still see this issue and you have new information that sheds some light feel free to re-open this issue and add the new info. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28727] CLOSE_WAIT connections draw 100 % cpu
https://issues.apache.org/bugzilla/show_bug.cgi?id=28727 Mark Thomas <[EMAIL PROTECTED]> changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Comment #23 from Mark Thomas <[EMAIL PROTECTED]> 2008-03-01 10:23:38 --- Re-closing as invalid based on last comment. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44516] New: Getting "Insufficient memory" frequently in Tomcat 5.5.23
https://issues.apache.org/bugzilla/show_bug.cgi?id=44516 Summary: Getting "Insufficient memory" frequently in Tomcat 5.5.23 Product: Tomcat 5 Version: 5.5.23 Platform: Sun OS/Version: SunOS Status: NEW Severity: critical Priority: P1 Component: Connector:AJP AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We are getting "Insufficient memory" frequently in Web Application running in Tomcat 5.5.23. The Memory and CPU Utilization by Tomcat Java process is increasing towards high over the period of time 4-5 hours after starting the server. The Memory component (RES & SIZE) both are increasing (1765M 1052M). After that Sever getting crashed and throwing "System Error: #148: Insufficient memory" We have 16G physical memory in the system and here is the Tomcat java process stack and Error stack provided below. Memory: 16G phys mem, 2436M free mem, 5000M total swap, 5000M free swap PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND 26581 webadmin 70 59 0 1765M 1052M sleep 26:00 1.05% java Notice: #450: Listening on MX_DEBUG_PORT 52117 System Error: #148: Insufficient memory System Error: #148: Insufficient memory System Error: #148: Insufficient memory Application is using TWO WEB and TWO APP servers running on "sun4v sparc SUNW,Sun-Fire-T200" Hardware. Each Web server box has one instance of Apache 2.2.3 and each App server box has one instance of Tomcat 5.5.23. Both Apache and Tomcat are coolstack binery version downloaded from SUM web site. NOTE: Apache config file (workers.properties) is being used to communicate between Web and App servers with cross connection. Each WEB server is communicates to two App servers. Server details: APP Server: lxks3e & lxks4e WEB Server: wex6e & wex7e Environment details: App Server : sun4v sparc SUNW,Sun-Fire-T200 (2 app servers) Web Server : sun4v sparc SUNW,Sun-Fire-T200 (2 web servers) OS Release : 5.10 Tomcat/ Apache/JDK ( Web Server : Apache/2.2.3 , App Server : Tomcat/5.5.23, http 1.1 ) JRE_HOME: /usr/jdk1.5.0_13 Server version: Apache Tomcat/5.5.23(coolstack binary) JDK Version Used : JDK1.5.0_13 JVM Version: 1.5.0_13-b05 JVM Vendor: Sun In the Tomcat startup script we are using the following "MX_JAVA_OPTIONS" parameter. MX_JAVA_OPTIONS="-server -Xss512k -Xms1280m -Xmx1280m -Djava.awt.headless=true -XX:NewSize=640m -XX:MaxNewSize=640m -XX:SurvivorRatio=3 -XX:PermSize=92m -XX:MaxPermSize=256m -XX:+UseParallelGC -XX:ParallelGCThreads=2 -XX:TargetSurvivorRatio=80 -XX:MaxTenuringThreshold=31" Please suggest how we can resolve this issue. Any help will be highly appreciated. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44516] Getting "Insufficient memory" frequently in Tomcat 5.5.23
https://issues.apache.org/bugzilla/show_bug.cgi?id=44516 Mark Thomas <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #1 from Mark Thomas <[EMAIL PROTECTED]> 2008-03-01 14:38:01 --- Looks like you app has a memory leak. You need to use the users list. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44517] New: web-app_2_4. xsd not up-to-date in TC6 servlet-api.jar
https://issues.apache.org/bugzilla/show_bug.cgi?id=44517 Summary: web-app_2_4.xsd not up-to-date in TC6 servlet-api.jar Product: Tomcat 6 Version: 6.0.14 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Maybe 18 months or more ago the web-app_2_4.xsd published by Sun was updated to correct the regex used to validate MIME types. When a validating XML parser is used and the old regex is used then errors result for trying to validate "text/xhtml+xml" due to the plus "+" character not being allowed by the old regex. xhtml application/xhtml+xml I would also motion that the Sun copyright notice should be retained in the file (and question if the Apache Foundation notice should appear at all, since claiming copyright on someone elses body of work doesn't seem legal ??? IANAL). There is also an original Sun version number shown near the top of the original XSD and would like to see this echo'ed in the Tomcat shipped version to help manage future updates to XSDs. In short the fix I am requesting is the following change: --- javax/servlet/resources/web-app_2_4.xsd 2008-03-02 00:49:56.0 + +++ ../web-app_2_4.xsd 2007-12-18 09:05:06.0 + @@ -805,7 +798,7 @@ - + I have checked Tomcat 5.5.x and that has already been updated (I believe I was involved in raising a bugzilla entry for it at the time, 18 months or so ago). I have checked Tomcat 6.0.x with regards to web-app_2_5.xsd and I can see that the one shipped with 6.0.14 is based on Sun's original XSD version 1.62 but now 1.68 is out. Maybe while you are at it the XSD for 2.5 could be brought up-to-date: -@(#)web-app_2_5.xsds1.62 05/08/06 + @(#)web-app_2_5.xsds 1.68 07/03/09 The originals are available here: http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
