[jboss-remoting-commits] JBoss Remoting SVN: r4246 - remoting2/branches/2.x/docs.

jboss-remoting-commits at lists.jboss.org jboss-remoting-commits at lists.jboss.org
Wed May 28 03:08:35 EDT 2008


Author: ron.sigal at jboss.com
Date: 2008-05-28 03:08:35 -0400 (Wed, 28 May 2008)
New Revision: 4246

Modified:
   remoting2/branches/2.x/docs/README.txt
Log:
JBREM-987: Added some JIRA issues.

Modified: remoting2/branches/2.x/docs/README.txt
===================================================================
--- remoting2/branches/2.x/docs/README.txt	2008-05-28 06:55:25 UTC (rev 4245)
+++ remoting2/branches/2.x/docs/README.txt	2008-05-28 07:08:35 UTC (rev 4246)
@@ -30,9 +30,50 @@
 in Jira, please create one.
 
 ==========================================================================================================
-Release Notes - JBoss Remoting - Version 2.4.0.CR2 - Text format
+Release Notes - JBoss Remoting - Version 2.4.0.GA
+
 Bug
 
+    * [JBREM-936] - CLONE [JBREM-915] - NullPointerException in InvokerLocator
+    * [JBREM-938] - CLONE [JBREM-937] - Callback BisocketServerInvoker should reuse available ServerThreads
+    * [JBREM-952] - CLONE [JBREM-944] - Fix race in ConnectionNotifier
+    * [JBREM-980] - ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator
+
+Feature Request
+
+    * [JBREM-773] - Create bisocket sample code
+    * [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted
+    * [JBREM-971] - Enhance server-side connection error handling so certain (potentially revealing) socket-related exceptins are not discarded
+    * [JBREM-979] - Add invocation retry facility to http transport
+    * [JBREM-983] - Legacy XML configuration should support multihome feature
+    
+Release
+
+    * [JBREM-987] - Release 2.4.0.GA
+
+Task
+
+    * [JBREM-238] - JBossRemoting testsuite needs to generate artificats in the output folder
+    * [JBREM-599] - remoting doc does not cover enabling or configuring leasing from the client side
+    * [JBREM-816] - Add instructions to Remoting Guide for overriding a transport or create a new transport
+    * [JBREM-840] - Update Remoting Guide for release 2.4.0
+    * [JBREM-920] - Create build.xml target to run test suite with a Security Manager
+    * [JBREM-930] - Fix chronic testsuite failures
+    * [JBREM-964] - Make InvocationFailureException extend java.rmi.MarshalException
+    * [JBREM-975] - Make sure all fixes on 2.2 branch are applied to 2.x branch
+    * [JBREM-976] - CLONE [JBREM-912] - Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
+    * [JBREM-977] - Wrap MBean proxies in security conscious wrappers
+    * [JBREM-978] - Put code subject to a security manager in privileged blocks, part 2
+    * [JBREM-982] - Performance testing
+    * [JBREM-984] - Run soak test
+    * [JBREM-985] - Assure version compatibility with earlier versions of Remoting
+    * [JBREM-986] - Make configurable time MicroSocketClientInvoker should wait to get connection from pool
+
+
+==========================================================================================================
+Release Notes - JBoss Remoting - Version 2.4.0.CR2
+Bug
+
     * [JBREM-947] - ConnectionValidator hangs when server dies
     * [JBREM-951] - CLONE [JBREM-942] - A deadlock encountered on ConnectionValidator
     * [JBREM-955] - CLONE [JBREM-954] - InterruptException should not be rethrown as CannotConnectionException
@@ -59,7 +100,6 @@
     * [JBREM-810] - coyote.RequestMap not storing all request properties in the Map.Entry set
     * [JBREM-826] - JBoss Remoting logs at ERROR and WARN in many places
     * [JBREM-844] - Put instance variable "isRemotingUserAgent" on stack in CoyoteInvoker
-    * [JBREM-898] - Fix encrypting marshaller/unmarshaller test cases
     * [JBREM-901] - can't start NetworkRegistry if hostname is not resolvable
     * [JBREM-924] - Compilation errors in non ISO-8859-1 systems
     * [JBREM-927] - Adjust content length when CompressingUnMarshaller wraps HTTPUnMarshaller
@@ -175,8 +215,6 @@
 Feature Request
 
     * [JBREM-298] - Need ability to add transport specific info to invocation payload
-    * [JBREM-480] - Insure reliable tests in socket invoker for unusable socket connections.
-    * [JBREM-639] - Allow stream factory to be specified for all transports
     * [JBREM-643] - configuration for multi-homed server invokers
     * [JBREM-701] - add timeout config per client invocation for transports not descended from socket transport
     * [JBREM-728] - Improve access to HTTP response headers
@@ -208,18 +246,13 @@
 
     * [JBREM-63] - Get rid of the legacy configuration that embeds xml parsing
     * [JBREM-228] - clustering
-    * [JBREM-364] - refactor client invoker config for common configurations
-    * [JBREM-475] - Eliminate ShutdownRequestThread in MultiplexingManager.
-    * [JBREM-554] - Let virtual MultiplexServerInvokers share master MultiplexServerInvoker's thread pool.
     * [JBREM-557] - need to include all the transports within the tests.versioning ant target
     * [JBREM-641] - re-implement the callback polling for http transport to reduce latency
     * [JBREM-687] - allow binding to 0.0.0.0
-    * [JBREM-699] - Extend the Marshaller/UnMarshaller interfaces by incorporating the PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces
     * [JBREM-706] - In socket transport, prevent client side oneway invocations from artificially reducing concurrency
     * [JBREM-710] - Correct occasional failures of org.jboss.test.remoting.transport.socket.load.SocketLoadTestCase
     * [JBREM-713] - Check if jbossweb can replace tomcat jars for the http server invoker
     * [JBREM-715] - Don't log error for exception thrown by application in org.jboss.remoting.transport.socket.ServerThread.
-    * [JBREM-729] - Make multiplex server invoker more robust
     * [JBREM-730] - JNDIDetector should use rebind() instead of bind() to add new local detection messages
     * [JBREM-733] - When org.jboss.remoting.Client.addListener() creates a Connector, it should pass in InvokerLocator parameters with configuration map.
     * [JBREM-734] - BisocketClientInvoker constructor should get parameters from InvokerLocator as well as configuration map.




More information about the jboss-remoting-commits mailing list