[Tomcat Wiki] Update of "FrontPage" by markt
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FrontPage" page has been changed by markt: https://wiki.apache.org/tomcat/FrontPage?action=diff&rev1=37&rev2=38 Comment: Add a link to the to be created events page * '''[[AddOns]]''' - Third party tools and add-ons not included in the official distribution * '''[[ReleaseProcess|Release Process]]''' - How to perform an official Apache Tomcat release * '''[[Development|Development Issues]]''' - Work in progress design and/or development documentation + * '''[[Events]]''' - Upcoming Tomcat events = Special Wiki pages = * '''HelpContents''' - A basic guide to the MoinMoin wiki (including information about wiki syntax). - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "Events" by markt
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "Events" page has been changed by markt: https://wiki.apache.org/tomcat/Events Comment: Create events page New page: ##language:en = Events = Information about upcoming Apache Tomcat events. * [[http://events.linuxfoundation.org/events/apachecon-north-america|ApacheCon North America, Denver, April 7-9, 2014]] * [[summit-na-2014|Apache Tomcat Summit, April 11, 2014]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "summit-na-2014" by markt
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "summit-na-2014" page has been changed by markt: https://wiki.apache.org/tomcat/summit-na-2014 New page: ##language:en = Apache Tomcat Summit = == Where: Denver, Colorado, USA == == When: Friday April 11, 2014 == Follows on from [[http://events.linuxfoundation.org/events/apachecon-north-america|ApacheCon NA 2014]] == Registration == Via the [[http://events.linuxfoundation.org/events/apachecon-north-america/program/schedule|ApacheCon NA 2014]] site. == Topics == The topics to be discussed will be finalized by the attendees on the day. The provisional list of topics is: * Road map for future development prior to the next round of JavaEE specifications * AJP support for HTTP upgrade * Please add your topics here... - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Other_Operating_Systems" by KonstantinKolinko
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Other_Operating_Systems" page has been changed by KonstantinKolinko: https://wiki.apache.org/tomcat/FAQ/Other_Operating_Systems?action=diff&rev1=4&rev2=5 Comment: Remove dead link Where are the scripts for my operating system? * OS/2: -* [[http://hobbes.nmsu.edu/cgi-bin/h-search?key=tomcat_5-0-27_os2.zip|NMSU.edu]] * [[http://www.netbeans.org/issues/show_bug.cgi?id=42678|NetBeans.org]] * [[http://issues.apache.org/bugzilla/show_bug.cgi?id=30394|EComStation]] * z/OS: @@ -19, +18 @@ * [[http://issues.apache.org/bugzilla/show_bug.cgi?id=31499|Hewlett Packard (meg.garri...@hp.com)]] - [[CategoryFAQ|CategoryFAQ]] + [[CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1573484 - in /tomcat/trunk: build.properties.default build.xml
Author: markt
Date: Mon Mar 3 09:10:13 2014
New Revision: 1573484
URL: http://svn.apache.org/r1573484
Log:
DBCP 2.0 has been released.
Modified:
tomcat/trunk/build.properties.default
tomcat/trunk/build.xml
Modified: tomcat/trunk/build.properties.default
URL:
http://svn.apache.org/viewvc/tomcat/trunk/build.properties.default?rev=1573484&r1=1573483&r2=1573484&view=diff
==
--- tomcat/trunk/build.properties.default (original)
+++ tomcat/trunk/build.properties.default Mon Mar 3 09:10:13 2014
@@ -152,14 +152,10 @@ tomcat-native.win.1=${base-tomcat.loc.1}
tomcat-native.win.2=${base-tomcat.loc.2}/tomcat-connectors/native/${tomcat-native.version}/binaries/tomcat-native-${tomcat-native.version}-win32-bin.zip
# - Commons DBCP, version 2.0 or later -
-#commons-dbcp.version=1.4
-#commons-dbcp.home=${base.path}/commons-dbcp-${commons-dbcp.version}-src
-#commons-dbcp-src.loc.1=${base-commons.loc.1}/dbcp/source/commons-dbcp-${commons-dbcp.version}-src.tar.gz
-#commons-dbcp-src.loc.2=${base-commons.loc.2}/dbcp/source/commons-dbcp-${commons-dbcp.version}-src.tar.gz
-commons-dbcp.version=2.0-20140228.204604-213
-commons-dbcp.home=${base.path}/commons-dbcp2-2.0-SNAPSHOT-src
-commons-dbcp-src.loc.1=https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-dbcp2/2.0-SNAPSHOT/commons-dbcp2-${commons-dbcp.version}-src.tar.gz
-commons-dbcp-src.loc.2=https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-dbcp2/2.0-SNAPSHOT/commons-dbcp2-${commons-dbcp.version}-src.tar.gz
+commons-dbcp.version=2.0
+commons-dbcp.home=${base.path}/commons-dbcp2-${commons-dbcp.version}-src
+commons-dbcp-src.loc.1=${base-commons.loc.1}/dbcp/source/commons-dbcp2-${commons-dbcp.version}-src.tar.gz
+commons-dbcp-src.loc.2=${base-commons.loc.2}/dbcp/source/commons-dbcp2-${commons-dbcp.version}-src.tar.gz
# - Commons Pool, version 2.1 or later -
commons-pool.version=2.2
@@ -167,8 +163,6 @@ commons-pool.home=${base.path}/commons-p
commons-pool-src.loc.1=${base-commons.loc.1}/pool/source/commons-pool2-${commons-pool.version}-src.tar.gz
commons-pool-src.loc.2=${base-commons.loc.2}/pool/source/commons-pool2-${commons-pool.version}-src.tar.gz
-
-
# - NSIS, version 2.0 or later -
nsis.home=${base.path}/nsis-2.46
nsis.exe=${nsis.home}/makensis.exe
Modified: tomcat/trunk/build.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/build.xml?rev=1573484&r1=1573483&r2=1573484&view=diff
==
--- tomcat/trunk/build.xml (original)
+++ tomcat/trunk/build.xml Mon Mar 3 09:10:13 2014
@@ -2576,8 +2576,6 @@ Apache Tomcat ${version} native binaries
-
-
[Tomcat Wiki] Update of "FAQ/Linux_Unix" by KonstantinKolinko
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Linux_Unix" page has been changed by KonstantinKolinko: https://wiki.apache.org/tomcat/FAQ/Linux_Unix?action=diff&rev1=10&rev2=11 Comment: Amend "Linux distributions" section That is because each of these packages distributes the files of Tomcat in different places on the disk, sets different environment variables, sets different links from one directory to the other in the filesystem, etc.. + Moreover, some of those packages are notably outdated. + So it would be better to install a "standard" tomcat downloaded from the website [[http://tomcat.apache.org/]], to some directory like `/opt/tomcat`, and follow the instructions that are given in the "RUNNING.txt" file. @@ -29, +31 @@ Several notes: - * Download a "binary" version. Either a "tar.gz" or a "zip" file is fine. There is usually no need to re-compile Tomcat from the source code. + * Download a "binary" version. There is usually no need to re-compile Tomcat from the source code. - * The "tar.gz" files use GNU extensions to the tar file format. You need a GNU-compatible version of `tar` to unpack them. + * Either a "tar.gz" or a "zip" file is fine. The "tar.gz" files use GNU extensions to the tar file format (as mentioned in "README" file in the download area). You need a GNU-compatible version of `tar` to unpack them. * Learn how to run Tomcat with separate values of `CATALINA_HOME` and `CATALINA_BASE`, as explained in "RUNNING.txt". This will simplify further upgrades and maintenance. <>'''When I run ps (on Linux), why do I see my java process a bazillion times!''' - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Linux_Unix" by KonstantinKolinko
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "FAQ/Linux_Unix" page has been changed by KonstantinKolinko:
https://wiki.apache.org/tomcat/FAQ/Linux_Unix?action=diff&rev1=11&rev2=12
Comment:
Document the effect of using non-GNU version of tar. Correct HTML markup: use
headers.
1. [[#Q2|How do I run without an X server and still get graphics?]]
1. [[#Q3|Tomcat dies after I log out!]]
1. [[#Q4|Catalina.log contains : "SEVERE: StandardServer.await: create[8005]
: Throwable occurred: java.net.BindException: The socket name is not available
on this system."]]
+ 1. [[#Q6|Examples web application does not start. A ClassNotFoundException
occurs.]]
== Answers ==
+
+ <>
- <>'''I have Tomcat x.y.z installed as part of my OS. Is it good
to use?'''
+ === I have Tomcat x.y.z installed as part of my OS. Is it good to use? ===
Many Linux distributions provide a pre-packaged version of Apache Tomcat.
@@ -35, +38 @@
* Either a "tar.gz" or a "zip" file is fine. The "tar.gz" files use GNU
extensions to the tar file format (as mentioned in "README" file in the
download area). You need a GNU-compatible version of `tar` to unpack them.
* Learn how to run Tomcat with separate values of `CATALINA_HOME` and
`CATALINA_BASE`, as explained in "RUNNING.txt". This will simplify further
upgrades and maintenance.
+ <>
- <>'''When I run ps (on Linux), why do I see my java process a
bazillion times!'''
+ === When I run ps (on Linux), why do I see my java process a bazillion times!
===
Linux implemented threads as processes. Due to other gory details that is
beyond the scope of this FAQ - the ps command doesn't work correctly with
respect to threads. You can get more gory details
[[http://www.onlamp.com/pub/a/onlamp/2002/11/07/linux_threads.html|here]] and
[[http://pauillac.inria.fr/~xleroy/linuxthreads/faq.html#D|here]] .
+ <>
- <>'''How do I run without an X server and still get graphics?'''
+ === How do I run without an X server and still get graphics? ===
You either need to run headless or run an alternate X-server. Some more
information can be found [[http://marc.info/?t=10480304763&r=1&w=2|here]],
[[http://marc.info/?l=tomcat-user&m=102335321103262&w=2|here]], or
[[http://marc.info/?l=tomcat-user&m=101614645312259&w=2|here]].
Or if your are using a JVM 1.4 or better, you can use the system property
{{{java.awt.headless=true}}}
- <>'''Tomcat dies after I log out!'''
+ <>
+ === Tomcat dies after I log out! ===
This is a common complaint when using Solaris. Make sure you use {{{nohup}}}
and see [[http://marc.info/?l=tomcat-user&m=104809785114238&w=2|this thread]]
- <>'''Error message: "SEVERE: StandardServer.await: create[8005]:
- Throwable occurred: java.net.BindException: The socket name is not available
on this system."'''
+ <>
+ === Error message: "SEVERE: StandardServer.await: create[8005]: Throwable
occurred: java.net.BindException: The socket name is not available on this
system." ===
This error message can have 2 causes:
1. Java on AIX isn't supporting IPv6 properly. Fix by inserting
{{{-Djava.net.preferIPv4Stack=true}}} into JAVA_OPTS
2. Your networking configuration is not correct. If you attempt to {{{ping
localhost}}} and don't see '''127.0.0.1''' you need to look into your
{{{/etc/host.conf}}} (most Unixes/Linux) or {{{/etc/netsvc.conf}}} (AIX) file
to ensure that something like ''"hosts = local, bind"'' is present.
+ <>
+ === Examples web application does not start. A ClassNotFoundException occurs.
===
+
+ Go into `webapps/examples/WEB-INF/classes` and check whether the class file
mentioned in the error message does exist.
+
+ If you downloaded a tar.gz file and used a non-GNU version of tar (e.g. on
Solaris) it may use wrong (truncated) file names on files that are deep in the
hierarchy. This occurs silently: there may be no error or warning during
unpacking. One place that is known to suffer from this is the examples web
application. The workaround is to download a "zip" file instead of a "tar.gz"
one. [[http://marc.info/?t=13935383126&r=1&w=2|thread]]
+
- [[CategoryFAQ|CategoryFAQ]]
+ [[CategoryFAQ]]
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Tomcat Wiki] Update of "FAQ/Linux_Unix" by KonstantinKolinko
Le 03/03/2014 11:21, Apache Wiki a écrit : > That is because each of these packages distributes the files of Tomcat > in different places on the disk, sets different environment variables, > sets different links from one directory to the other in the filesystem, > etc.. > + Moreover, some of those packages are notably outdated. But some people try hard to make them current ! :) Tomcat 7.0.52 is in Debian unstable [1] and I plan to backport it to the stable distribution which is stuck with 7.0.28 + security fixes. The package for Tomcat 8 is ready [2] and will be uploaded once EasyMock has been upgraded. Emmanuel Bourg [1] https://packages.debian.org/sid/tomcat7 [2] http://anonscm.debian.org/gitweb/?p=pkg-java/tomcat8.git - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56190] Connection keep-alive not working with asynchronous servlet
https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Konstantin Kolinko changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #7 from Konstantin Kolinko --- 1. I agree that "closing the response that was used to initialize this AsyncContext." seems to be missing from AsyncContextImpl.complete() [[[ request.getCoyoteRequest().action(ActionCode.COMMIT, null); request.getCoyoteRequest().action(ActionCode.ASYNC_COMPLETE, null); clearServletRequestResponse(); ]]] 2. It is unclear whether this "commit" and "closing the response" have to occur before firing onComplete() event or after it. It it has to be committed before firing and closed after firing, you would get the chunked response. To get a non-chunked response, one has to close the response without an explicit commit. Either (close before firing) or (non commit before firing + close after firing). I am reading that onComplete() is designed to allow cleanup of some resources, so I think that response can be closed before firing. (Though it will break applications that expect otherwise. Are there are any?) 3. There is a workaround for your example: Close the response explicitly, [[[ response.getWriter().close() ]]] You should get a non-chunked response this way. -- 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
[Bug 56208] New: validateXml attribute is missing in jasper Ant Task (JspC) in 6.0.39, 7.0.52
https://issues.apache.org/bugzilla/show_bug.cgi?id=56208 Bug ID: 56208 Summary: validateXml attribute is missing in jasper Ant Task (JspC) in 6.0.39, 7.0.52 Product: Tomcat 6 Version: 6.0.39 Hardware: All OS: All Status: NEW Severity: regression Priority: P2 Component: Jasper Assignee: dev@tomcat.apache.org Reporter: knst.koli...@gmail.com Mail threads: http://tomcat.markmail.org/thread/4gblbbzxltq5jpzw http://tomcat.markmail.org/thread/ydrqotnjkmdl6err http://tomcat.markmail.org/thread/sn5gkulktf7tteon This has already been fixed in Tomcat 7 by r1570163 and will be in 7.0.53. Note that starting with 7.0.53 "validateXml" and "validateTld" are two distinct options. As of now "validateXml" option is removed from Tomcat 8 since 8.0.3 onwards. Some pending cleanup and discussion on whether to reimplement in Tomcat 8 is tracked as bug 56199. If you are using validateXml="false", my recommendation is to just remove that attribute from your build files. (It does not serve anything, as "false" is the default value for this attribute). A backport of r1570163 has been proposed for 6.0 -- 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: r1573533 - /tomcat/tc6.0.x/trunk/STATUS.txt
Author: kkolinko Date: Mon Mar 3 12:13:14 2014 New Revision: 1573533 URL: http://svn.apache.org/r1573533 Log: Correct bug number Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=1573533&r1=1573532&r2=1573533&view=diff == --- tomcat/tc6.0.x/trunk/STATUS.txt (original) +++ tomcat/tc6.0.x/trunk/STATUS.txt Mon Mar 3 12:13:14 2014 @@ -40,8 +40,7 @@ PATCHES PROPOSED TO BACKPORT: +1: kkolinko -1: -* Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=56199 - http://tomcat.markmail.org/thread/ydrqotnjkmdl6err +* Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=56208 Restore validateXml option in Jasper. Motivation: It is mentioned in documentation and some users complained on removal of this option in Tomcat 7, as that broke their build scripts. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1573535 - /tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
Author: kkolinko Date: Mon Mar 3 12:15:13 2014 New Revision: 1573535 URL: http://svn.apache.org/r1573535 Log: Bug number for r1570163 Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml URL: http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml?rev=1573535&r1=1573534&r2=1573535&view=diff == --- tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml (original) +++ tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Mon Mar 3 12:15:13 2014 @@ -52,7 +52,7 @@ There is no ordering by add/update/fix. Other fixed issues are added to the end of the list, chronologically. - They eventually become mixed with the numbered issues. (I.e., numbered +4 They eventually become mixed with the numbered issues. (I.e., numbered issues to not "pop up" wrt. others). --> @@ -82,15 +82,16 @@ +55483: Improve handing of overloaded methods and constructors +in expression language implementation. (markt) + + +56208: Restore the validateXml option to Jasper that was previously renamed validateTld. Both options are now supported. validateXml controls the validation of web.xml files when Jasper parses them and validateTld controls the validation of *.tld files when Jasper parses them. (markt) - -55483: Improve handing of overloaded methods and constructors -in expression language implementation. (markt) - - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn propchange: r1570163 - svn:log
Author: kkolinko Revision: 1570163 Modified property: svn:log Modified: svn:log at Mon Mar 3 12:16:01 2014 -- --- svn:log (original) +++ svn:log Mon Mar 3 12:16:01 2014 @@ -1 +1,2 @@ +Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=56208 Restore the validateXml option to Jasper that was previously renamed validateTld. Both options are now supported. validateXml controls the validation of web.xml files when Jasper parses them and validateTld controls the validation of *.tld files when Jasper parses them. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56199] Re-implement validateXml option in JspC of Tomcat 8, or remove it from documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=56199 Konstantin Kolinko changed: What|Removed |Added Summary|Implement validateXml |Re-implement validateXml |option in JspC, or remove |option in JspC of Tomcat 8, |it from documentation |or remove it from ||documentation OS||All --- Comment #1 from Konstantin Kolinko --- This bug is about re-implementing this feature in Tomcat 8, or cleaning up docs if the feature is not implemented. Related issue in Tomcat 6 and 7 is tracked as bug 56208. -- 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: r1573538 - /tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
Author: kkolinko Date: Mon Mar 3 12:21:41 2014 New Revision: 1573538 URL: http://svn.apache.org/r1573538 Log: Revert occasional typo. Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml URL: http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml?rev=1573538&r1=1573537&r2=1573538&view=diff == --- tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml (original) +++ tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Mon Mar 3 12:21:41 2014 @@ -52,7 +52,7 @@ There is no ordering by add/update/fix. Other fixed issues are added to the end of the list, chronologically. -4 They eventually become mixed with the numbered issues. (I.e., numbered + They eventually become mixed with the numbered issues. (I.e., numbered issues to not "pop up" wrt. others). --> - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Tomcat Wiki] Update of "FAQ/Linux_Unix" by KonstantinKolinko
On 03/03/14 11:16, Emmanuel Bourg wrote: Le 03/03/2014 11:21, Apache Wiki a écrit : That is because each of these packages distributes the files of Tomcat in different places on the disk, sets different environment variables, sets different links from one directory to the other in the filesystem, etc.. + Moreover, some of those packages are notably outdated. But some people try hard to make them current ! :) That is good to hear! Tomcat 7.0.52 is in Debian unstable [1] and I plan to backport it to the stable distribution which is stuck with 7.0.28 + security fixes. The package for Tomcat 8 is ready [2] and will be uploaded once EasyMock has been upgraded. I like the way the debian/ubuntu package installs, but I moved away from 7.0.28 a very long time ago. My present strategy is to build my preferred version (currently 7.0.52) from source, then deploy it to replace the 7.0.28 specific content. Using CATALINA_HOME and CATALINA_BASE as recommended by the tc-devs certainly makes this approach less painful. As you will have noticed already, the main responders on the tc-users list have learned the hard way that it is difficult to help people who are stuck on an obsolete version because they took the "safe and easy" option to install their O/S distribution maintainer's "stable" package. If you need some help (perhaps QA testing), please let me know. Thanks for the work so far, and the good intentions! Brian Emmanuel Bourg [1] https://packages.debian.org/sid/tomcat7 [2] http://anonscm.debian.org/gitweb/?p=pkg-java/tomcat8.git - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat Connectors 1.2.39
On 28.02.2014 10:35, Mladen Turk wrote: > Apache Tomcat Connectors 1.2.39 release candidate is ready > for vote at [1]. The build was done using tag [2]. > This version fixes few bugs found in released > version 1.2.37 and adds some new features like IPV6 support. > > > The VOTE will remain open for at least 48 hours. > > The Apache Tomcat Connectors 1.2.39 is > [X] Stable, go ahead and release > [ ] Broken because of ... +1 Details: - Sigs and hashes OK - key in KEYS file - key is only signed by Jean-Frederic, would be good to find a few more people to sign it for the web of trust - gz and zip for src identical - src consistent with svn tag, except for the following expected deltas: - LICENSE and NOTICE moved one directory up (OK) - KEYS not in dist (OK) - deprectated jk2 xdocs missing in dist (OK) - additional generated files in dist: aclocal.m4, configure, Makefile.in, config.h.in, html docs in dist (OK) - additional auto tool copied files in dist: install-sh, ltmain.sh, missing (OK) - build.properties.autoconf, native/build.xml and the jkant directory missing from dist. Builds succesfully on all tested platforms: - Solaris 8 Sparc using gcc 4.1.2 as 32 Bit Binaries for 1.3, 2.0, 2.2 - Solaris 10 Sparc using gcc 4.8.2 as 32 Bit Binaries for 2.4 - SLES 10 64 bit using platform gcc for 1.3, 2.0, 2.2 - SLES 10 32 bit using platform gcc for 2.2 - SLES 11 64 bit using platform gcc for 2.2, 2.4 - RHEL 5 64bit using platform gcc for 2.2 - SLES 6 64 bit using platform gcc for 2.2, 2.4 using CFLAGS: -O2 -g -Wall -fno-strict-aliasing (and -mpcu=v9 on Solaris) Additional observations (not a regression, affected file list slightly different from 1.2.37): The README, *.pdb, *.dll and *.so files contained in the binary zips for Windows extract as owner and group writable for me on Unix (even when using umask 022). All other files are OK. Maybe some possible improvement of setting the perms after build and before zipping. i don't see such problems in the src zip. File ltmain.sh in src tar and zip has perms 644 instead of 755 (not a regression). Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat Connectors 1.2.39
On 03/03/2014 02:10 PM, Rainer Jung wrote: On 28.02.2014 10:35, Mladen Turk wrote: The README, *.pdb, *.dll and *.so files contained in the binary zips for Windows extract as owner and group writable for me on Unix (even when using umask 022). I did that on purpose. There was some problems if using cygwin zip to uncompress those files. If it's not 664 and 775 it will set some weird security settings on those files making them unloadable by IIS. Cheers -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56213] New: Many KeyReference Objects Cause Long CMS-remark GC Times
https://issues.apache.org/bugzilla/show_bug.cgi?id=56213 Bug ID: 56213 Summary: Many KeyReference Objects Cause Long CMS-remark GC Times Product: Tomcat 7 Version: 7.0.47 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Connectors Assignee: dev@tomcat.apache.org Reporter: jmid...@gmail.com This is a request to prop the following fix to Tomcat 7. http://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1388890 Using the NIO connector with a WebSocket application many (millions of) KeyReference objects are created under traffic. While the objects are small, the sheer number of them seems to overwhelm the CMS collector. Before the above fix with our application the CMS remark stop the world phase was taking up to 8.8 seconds. 716.463: [GC[YG occupancy: 213377 K (392896 K)]716.463: [Rescan (parallel) , 5.7904380 secs]722.253: [weak refs processing, 2.3101000 secs] [1 CMS-remark: 1160677K(1703936K)] 1374054K(2096832K), 8.8005960 secs] [Times: user=107.17 sys=0.00, real=8.80 secs] Total time for which application threads were stopped: 8.8020690 seconds After applying the fix under the same traffic the time drops to 110ms. 1282.459: [GC[YG occupancy: 203760 K (392896 K)]1282.459: [Rescan (parallel) , 0.0594610 secs]1282.519: [weak refs processing, 0.0452530 secs] [1 CMS-remark: 1159948K(1703936K)] 1363708K(2096832K), 0.1084940 secs] [Times: user=1.12 sys=0.00, real=0.11 secs] Total time for which application threads were stopped: 0.1100650 seconds For a real time application the 9 second pause is a killer. These tests were executed under: RHEL 6.4 java version "1.6.0_65" Java(TM) SE Runtime Environment (build 1.6.0_65-b14-BR8013809) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04, mixed mode) With the following JVM parms: -server -XX:NewSize=384m -XX:MaxNewSize=384m -XX:+UseParNewGC -XX:MaxTenuringThreshold=0 -Xms2048m -Xmx2048m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=68 -XX:+UseCMSInitiatingOccupancyOnly -XX:PermSize=96m -XX:MaxPermSize=96m -XX:+UseMembar -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintClassHistogram -- 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
