|
From: <zy...@us...> - 2010-09-13 17:53:12
|
Revision: 7122
http://jython.svn.sourceforge.net/jython/?rev=7122&view=rev
Author: zyasoft
Date: 2010-09-13 17:53:05 +0000 (Mon, 13 Sep 2010)
Log Message:
-----------
Updated NEWS and README.txt in prep of 2.5.2b2
Modified Paths:
--------------
trunk/jython/NEWS
trunk/jython/README.txt
Modified: trunk/jython/NEWS
===================================================================
--- trunk/jython/NEWS 2010-09-13 13:44:33 UTC (rev 7121)
+++ trunk/jython/NEWS 2010-09-13 17:53:05 UTC (rev 7122)
@@ -2,6 +2,7 @@
Jython 2.5.2b2
Bugs Fixed
+ - [ 1327 ] Classloaders cannot GC, which exhausts permgen (partial bug fix)
- [ 1604 ] PyBuiltinCallable.Info should be serializable
- [ 1397 ] Bugs in PyList and PyJavaType.ListIndexDelegate slice setting
- [ 1503 ] Java constructors should take keyword arguments
Modified: trunk/jython/README.txt
===================================================================
--- trunk/jython/README.txt 2010-09-13 13:44:33 UTC (rev 7121)
+++ trunk/jython/README.txt 2010-09-13 17:53:05 UTC (rev 7122)
@@ -1,13 +1,43 @@
Welcome to Jython 2.5.2 Beta2
=============================
-This is the second beta release of the 2.5.2 version of Jython. This release
-fixes a number of bugs and addresses memory and threading issues. See the NEWS file for
-more details.
+This is the second beta release of the 2.5.2 version of Jython. Our
+current plans is that this will be the last beta of 2.5.2, but this
+will depend on bug report.
-The release was compiled on Mac OS X with JDK 5 and requires JDK 5 to run.
+This release fixes bugs related to resource leaks, Java integration,
+and a number of other issues. See the NEWS file for more details. In
+particular, we did not completely fix #1327, "Classloaders cannot GC,
+which exhausts permgen." Jython uses instances of ThreadLocal-managed
+class, ThreadState, to manage its execution state, including frames,
+exceptions, and the global namespace. The ThreadState also indirectly
+refers to the ClassLoaders used by Jython. Such usage can cause
+resource leaks when a Jython application is restarted under certain
+app containers, because the ThreadState often may not cleaned up by
+the app server's thread pool.
-Please try it out and report any bugs at http://bugs.jython.org.
+Fixing this problem without a breakwards breaking API change appears
+to be difficult. Therefore we recommend exploring workarounds, such as
+the one published in this blog post,
+http://weblogs.java.net/blog/jjviana/archive/2010/06/09/dealing-glassfish-301-memory-leak-or-threadlocal-thread-pool-bad-ide
-And - last but not least - please help spread the word:
-If companies still are using Jython 2.2.1, they really should start testing against 2.5.2 now.
+Jython 2.6 will introduce limited backwards breaking API changes, so
+it will be possible to fully resolve this bug, and related issues, in
+that version instead.
+
+And -- last but not least -- please help spread the word:
+
+Organizations using Jython 2.2.1, or earlier, should test their code
+against 2.5.2 beta 2 now so that bug fixes and/or workarounds may be
+identified. In particular, please note the following:
+
+ * No additional work is anticipated on Jython 2.2.
+
+ * Jython 2.5.2 is the last release in Jython 2.5.x series that will
+ address non-severe issues, including Java integration issues.
+
+ * Jython 2.6 development will begin immediately following the 2.5.2
+ release. Jython 2.6 will require the use of JDK 6.
+
+The release was compiled on Mac OS X with JDK 5 and requires JDK 5 to
+run. Please try it out and report any bugs at http://bugs.jython.org.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|