[ANN] Apache Tomcat 7.0.14 released
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.14. Apache Tomcat 7.0.14 includes bug fixes and the following new features compared to version 7.0.12: - new StuckThreadDetectionValve to identify long running requests - JAAS authentication support for the JMXRemoteLifecycleListener - updated MIME type mappings to align with those of Apache httpd Please refer to the change log for the list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html Note that this version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures. Downloads: http://tomcat.apache.org/download-70.cgi Migration guide from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html Thank you, -- The Apache Tomcat Team - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51195] New: "Find leaks" reports a false positive memory/classloader leak
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195 Bug #: 51195 Summary: "Find leaks" reports a false positive memory/classloader leak Product: Tomcat 7 Version: 7.0.12 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Manager AssignedTo: dev@tomcat.apache.org ReportedBy: jhuxh...@googlemail.com Classification: Unclassified If a webapp is using serialization of classes loaded by the webapp classloader then the "Find leaks" button will report a leak after undeploy of the webapp. This is only partially true since the references that are still kept are only SoftReference instances. This can be circumvented by adding code comparable to the changes in this commit https://github.com/huxi/logback/commit/d53e970963f84692889d438dd8a23c96137c15f2 prior to executing the garbage collection during "Find leaks". I'd suggest to add such code to prevent the false positive warning. See also http://jira.qos.ch/browse/LBCORE-205 -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51195] "Find leaks" reports a false positive memory/classloader leak
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195 Konstantin Kolinko changed: What|Removed |Added OS/Version||All Severity|normal |enhancement -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1102674 - in /tomcat/site/trunk: docs/doap_Tomcat.rdf xdocs/doap_Tomcat.rdf
Author: kkolinko Date: Fri May 13 11:15:40 2011 New Revision: 1102674 URL: http://svn.apache.org/viewvc?rev=1102674&view=rev Log: Update doap file with new release info. Modified: tomcat/site/trunk/docs/doap_Tomcat.rdf tomcat/site/trunk/xdocs/doap_Tomcat.rdf Modified: tomcat/site/trunk/docs/doap_Tomcat.rdf URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/doap_Tomcat.rdf?rev=1102674&r1=1102673&r2=1102674&view=diff == --- tomcat/site/trunk/docs/doap_Tomcat.rdf (original) +++ tomcat/site/trunk/docs/doap_Tomcat.rdf Fri May 13 11:15:40 2011 @@ -55,8 +55,8 @@ Latest Stable 7.0.x Release -2011-04-06 -7.0.12 +2011-05-12 +7.0.14 Modified: tomcat/site/trunk/xdocs/doap_Tomcat.rdf URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/doap_Tomcat.rdf?rev=1102674&r1=1102673&r2=1102674&view=diff == --- tomcat/site/trunk/xdocs/doap_Tomcat.rdf (original) +++ tomcat/site/trunk/xdocs/doap_Tomcat.rdf Fri May 13 11:15:40 2011 @@ -55,8 +55,8 @@ Latest Stable 7.0.x Release -2011-04-06 -7.0.12 +2011-05-12 +7.0.14 - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1102689 - in /tomcat/site/trunk: docs/oldnews.html xdocs/oldnews.xml
Author: kkolinko Date: Fri May 13 12:19:37 2011 New Revision: 1102689 URL: http://svn.apache.org/viewvc?rev=1102689&view=rev Log: Resurrect old news since 7.0.0, because some of them had important highlights (e.g. 7.0.12), but remove their standard Changelog and Download links that become obsolete when a new version comes out. Modified: tomcat/site/trunk/docs/oldnews.html tomcat/site/trunk/xdocs/oldnews.xml Modified: tomcat/site/trunk/docs/oldnews.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/oldnews.html?rev=1102689&r1=1102688&r2=1102689&view=diff == --- tomcat/site/trunk/docs/oldnews.html (original) +++ tomcat/site/trunk/docs/oldnews.html Fri May 13 12:19:37 2011 @@ -197,6 +197,235 @@ + + + + +Tomcat 7.0.12 Released + + + + + +2011-04-06 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.12 of +Apache Tomcat. This release includes bug fixes, security fixes and the following +new features compared to version 7.0.11: + +initial support for SPNEGO/Kerberos authentication (also referred to as +Windows authentication); +provide a new configuration option to define a close method to call on a +JNDI resource when it is no longer required; +optional support for pre-emptive authentication. + +Full details of these changes, and all the other changes, are available in the +Tomcat 7 changelog. + + + + + + + + + + + + + + + + + + + +Tomcat 7.0.11 Released + + + + + +2011-03-11 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.11 of +Apache Tomcat. This release includes bug fixes and a security fix over Apache +Tomcat 7.0.10. + + + + + + + + + + + + + + + + + + +Tomcat 7.0.10 Released + + + + + +2011-03-07 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.10 of +Apache Tomcat. This release includes bug fixes and a security fix over Apache +Tomcat 7.0.8. + + + + + + + + + + + + + + + + + + +Tomcat 7.0.8 Released + + + + + +2011-02-05 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.8 of +Apache Tomcat. This release includes security and bug fixes over Apache Tomcat +7.0.6. + + + + + + + + + + + + + + + + + + +Tomcat 5.5.32 Released + + + + + +2011-02-01 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 5.5.32 of +Apache Tomcat. This release includes many bug fixes and a number of security +fixes over Apache Tomcat 5.5.31. + + + + + + + + + + + + + + + + + + + +Tomcat 7.0.6 Released + + + + + +2011-01-14 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.6 of +Apache Tomcat. This is the first stable release of the Tomcat 7 branch. This +release contains a number of bug fixes, further performance improvements in +session management and several enhancements to the memory leak detection and +prevention features. + + + + + + + + + + + + + + @@ -218,11 +447,121 @@ The Apache Tomcat Project is proud to announce the release of version 6.0.30 of Apache Tomcat. This release includes bug fixes over Apache Tomcat 6.0.29. - - -Download | -ChangeLog for 6.0.30 + + + + + + + + + + + + + + + + + + +Tomcat 7.0.5 Released + + + + + +2010-12-01 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.5 beta +of Apache Tomcat. This release contains a number of bug fixes, performance +improvements in session management, a number of new features including support +for parallel deployment of multiple versions of the same web application and a +redesigned welcome page. + + + + + + + + + + + + + + + + + + +Tomcat 7.0.4 Released + + + + + +2010-10-21 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 7.0.4 beta +of Apache Tomcat. This version of Apache Tomcat supports the +Servlet 3.0, JSP 2.2 and EL 2.2 specifications. In addition, it includes +numerous other improvements such as web application memory leak detection and +prevention, extensive internal code clean-up and support for including external +content directly in a web application (aliases). This release includes many +bug fixes over Apache Tomcat 7.0.2. + + + + + + + + + + + + + + + + + + +Tomcat 5.5.31 Released + + + + + +2010-09-16 + + + + + + + + +The Apache Tomcat Project is proud to announce the release of version 5.5.31 of +Apache Tomcat. This release includes many bug fixes and a number of security +fixes over Apache Tomcat 5.5.30. @@ -263,10 +602,6 @@ Servlet 3.0, JSP 2.2 and EL 2.2 specific numerous other improvements such as web application memory leak detection and prevention, extensive internal code clean-up and support for including external content directly in a web application (aliases). - -Download | -ChangeLog for 7.0.2 - @@ -302,11 +637,6 @@ content directly in a web application (a The Apache Tomcat Project is pr
DO NOT REPLY [Bug 51197] New: sendError/sendRedirect don't work with AsyncContext
https://issues.apache.org/bugzilla/show_bug.cgi?id=51197 Bug #: 51197 Summary: sendError/sendRedirect don't work with AsyncContext Product: Tomcat 7 Version: 7.0.14 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: Servlet & JSP API AssignedTo: dev@tomcat.apache.org ReportedBy: dchecko...@gmail.com Classification: Unclassified For some reason, response.sendRedirect and response.sendError are not producing expected behavior when using an AsyncContext. On the server side, the async request completes normally, and everything looks hunky dory, but the client never gets ANY response from the server. It appears that Tomcat simply times out after the default 10 seconds and closes the connection. No headers are returned, no content, nothing. I've confirmed with thread dumps that the server isn't stuck. Yet...if you use response.setStatus and response.setHeader instead, it works absolutely fine. The client gets the response every time. I put together a very simple test that isolates the issue reliably: https://github.com/dcheckoway/async-test See the README in there for details. NOTE: the behavior for sendError changed slightly from 7.0.12 to 7.0.14. As of 7.0.14, sendError seems to close the connection immediately, but the client still never gets any response of any kind. -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51197] sendError/sendRedirect don't work with AsyncContext
https://issues.apache.org/bugzilla/show_bug.cgi?id=51197 --- Comment #1 from Dan Checkoway 2011-05-13 12:52:10 UTC --- Forgot to mention, I use the NIO connector: -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51198] New: Trunk Version : Performance enhancement in ConnectionPool regarding busy Queue
https://issues.apache.org/bugzilla/show_bug.cgi?id=51198 Bug #: 51198 Summary: Trunk Version : Performance enhancement in ConnectionPool regarding busy Queue Product: Tomcat Modules Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: jdbc-pool AssignedTo: dev@tomcat.apache.org ReportedBy: p.moua...@ubik-ingenierie.com Classification: Unclassified Created attachment 26997 --> https://issues.apache.org/bugzilla/attachment.cgi?id=26997 The fix Hello, I am making Load Tests under the current trunk version(20110513) of the Pool. Looking at code I noticed the following TODO: TODO - this shouldn't be a blocking queue, simply a list to hold our objects I implemented the change and performances seem better so I submit the patch. Regards Philippe Mouawad http://www.ubik-ingenierie.com -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51198] Trunk Version : Performance enhancement in ConnectionPool regarding busy Queue
https://issues.apache.org/bugzilla/show_bug.cgi?id=51198 Philippe Mouawad changed: What|Removed |Added CC||p.mouawad@ubik-ingenierie.c ||om -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51088] ArrayIndexOutOfBoundsException from org.apache.el.parser.JJTELParserState
https://issues.apache.org/bugzilla/show_bug.cgi?id=51088
--- Comment #3 from Konstantin Kolinko 2011-05-13
22:46:16 UTC ---
> Unfortunately it is not reproducible at all.
a) Some rarely executed if-branch in [/facelets/myview.xhtml]?
Rare things are not that rare. I do not see any other reports of such an issue
with JJTELParserState.
b) Concurrency? As Mark noted in Comment 1 this is unlikely.
ExpressionBuilder.java:115 is creating a new ELParser for a String and parsing
it. That parsing should be thread safe.
>n = (new ELParser(new StringReader(expr)))
>.CompositeExpression();
c) Unexpected JVM Error? E.g. OutOfMemoryError.
The ELParser.java:74 is inside a finally{} block, so if this happened during
exception processing the original error might be lost. I think the following
cascade of errors is possible, where original error is masked by two others:
1. Exception at ELParser.java:74 (jjtree.closeNodeScope(jjtn000, true);) is
possible only if jjtc000 is true.
2. I think that before it at ELParser.java:60 (jjtree.clearNodeScope(jjtn000);)
call failed with a RuntimeException e.g. for the same wrong index reasons as 1.
and failed to set jjtc000 to false.
3. The 2. is inside a catch(Throwable) block and it might be triggered by an
OutOfMemoryError, (or by another RuntimeException at the lower layer, because
the same catch(Throwable)+finally handling is everywhere in that generated
code).
I think c) is feasible.
--
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: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
