[jboss-remoting-commits] JBoss Remoting SVN: r4318 - remoting2/branches/2.2/docs/guide/en.
jboss-remoting-commits at lists.jboss.org
jboss-remoting-commits at lists.jboss.org
Mon Jun 23 19:01:09 EDT 2008
Author: ron.sigal at jboss.com
Date: 2008-06-23 19:01:08 -0400 (Mon, 23 Jun 2008)
New Revision: 4318
Modified:
remoting2/branches/2.2/docs/guide/en/chap16.xml
Log:
JBREM-948: Added 2.2.2.SP8 release notes.
Modified: remoting2/branches/2.2/docs/guide/en/chap16.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap16.xml 2008-06-23 22:38:51 UTC (rev 4317)
+++ remoting2/branches/2.2/docs/guide/en/chap16.xml 2008-06-23 23:01:08 UTC (rev 4318)
@@ -16,9 +16,227 @@
<para></para>
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP8</para>
+
+<para>Bug</para>
+
+ <para>* [JBREM-949] - CLONE [JBREM-947] - ConnectionValidator hangs when server dies</para>
+ <para>* [JBREM-954] - InterruptedException should not be rethrown as CannotConnectionException</para>
+ <para>* [JBREM-960] - Remoting configured with Servlet invoker can return misleading Exceptions when Servlet path is incorrect</para>
+ <para>* [JBREM-962] - Remote classloading does not work with Isolated EARs</para>
+ <para>* [JBREM-965] - Fix PortUtil.getRandomStartingPort()</para>
+ <para>* [JBREM-981] - CLONE [JBREM-980] - ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator</para>
+ <para>* [JBREM-1003] - Verify IPv6 addresses are handled correctly, part 2</para>
+
+<para>Feature Request</para>
+
+ <para>* [JBREM-972] - CLONE [JBREM-971] - Enhance client-side connection error handling so certain (potentially revealing) socket-related exceptins are not discarded </para>
+ <para>* [JBREM-973] - CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted</para>
+
+<para>Release</para>
+
+ <para>* [JBREM-948] - Release 2.2.0.SP8</para>
+
+<para>Task</para>
+
+ <para>* [JBREM-950] - Assure version compatibility with earlier versions of Remoting</para>
+ <para>* [JBREM-995] - Apply unit test timing fixes</para>
+ <para>* [JBREM-1001] - Update Remoting Guide</para>
+ <para>* [JBREM-1002] - Allow ServerThread to keep running after SocketTImeoutException, part 2</para>
+ <para>* [JBREM-1004] - Run manual servlet unit tests</para>
+
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP7</para>
+
+<para>Bug</para>
+
+ <para>* [JBREM-942] - A deadlock encountered on ConnectionValidator</para>
+ <para>* [JBREM-944] - Fix race in ConnectionNotifier</para>
+
+<para>Release</para>
+
+ <para>* [JBREM-943] - Release 2.2.0.SP7</para>
+
+<para>Task</para>
+
+ <para>* [JBREM-945] - Allow ServerThread to keep running after SocketTImeoutException</para>
+ <para>* [JBREM-946] - Assure version compatibility with earlier versions of Remoting</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP6</para>
+
+<para>Bug</para>
+
+ <para>* [JBREM-915] - NullPointerException in InvokerLocator</para>
+ <para>* [JBREM-937] - Callback BisocketServerInvoker should reuse available ServerThreads</para>
+
+<para>Release</para>
+
+ <para>* [JBREM-939] - Release 2.2.2.SP6</para>
+
+<para>Task</para>
+
+ <para>* [JBREM-940] - Assure version compatibility with earlier versions of Remoting</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP5</para>
+<para>Bug</para>
+
+ <para>* [JBREM-892] - CLONE -Client side connection exception is not thrown on the client side when the lease times out [JBREM-888]</para>
+ <para>* [JBREM-910] - CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909]</para>
+
+<para>Release</para>
+
+ <para>* [JBREM-913] - Release 2.2.2.SP5</para>
+
+<para>Task</para>
+
+ <para>* [JBREM-912] - Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP4</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-823] - ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6</para>
+ <para>* [JBREM-845] - Infinite loop in BisocketClientInvoker.createSocket</para>
+ <para>* [JBREM-858] - MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools</para>
+ <para>* [JBREM-860] - Eliminate delay in MicroSocketClientInvoker.getConnection()</para>
+ <para>* [JBREM-871] - HTTP Client invoker doesn't throw exceptions when using the sslservlet protocol</para>
+
+
+<para>** Feature Request</para>
+ <para>* [JBREM-852] - Verify IPv6 addresses are handled correctly</para>
+ <para>* [JBREM-855] - Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4</para>
+ <para>* [JBREM-873] - Have ServerInvokerCallbackHandler register as connection listener</para>
+
+<para>** Release</para>
+ <para>* [JBREM-872] - Release 2.2.0.SP4</para>
+
+<para>** Task</para>
+ <para>* [JBREM-862] - Verify compatibility with earlier versions</para>
+
+<para>==========================================================================================================</para>
+<para>N.B. Release 2.2.2.SP4 replaces 2.2.2.SP3.</para>
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP2</para>
+<para>Bug</para>
+
+ <para>* [JBREM-811] - Privileged Block to create Class Loader</para>
+ <para>* [JBREM-813] - ServletServerInvoker should return an exception instead of just an error message</para>
+
+<para>Release</para>
+
+ <para>* [JBREM-817] - Release 2.2.2.SP2</para>
+
+<para>Task</para>
+
+ <para>* [JBREM-687] - allow binding to 0.0.0.0</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.SP1</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-653] - allow user to set content-type for http responses</para>
+ <para>* [JBREM-750] - Logger in HTTPClientInvoker should be static.</para>
+
+<para>** Release</para>
+ <para>* [JBREM-803] - Release 2.2.2.SP1</para>
+
+<para>** Task</para>
+ <para>* [JBREM-805] - Verify Remoting 2.2.2.SP1 is compatible with earlier versions</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.2.GA</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-731] - Address of secondary server socket should be acquired each time a control connection is created.</para>
+ <para>* [JBREM-743] - For polling callback handler, org.jboss.remoting.Client.addListener() should create only one CallbackPoller per InvokerCallbackHandler</para>
+ <para>* [JBREM-747] - org.jboss.remoting.transport.Connector should unregister server invoker from MBeanServer</para>
+ <para>* [JBREM-754] - Reset timeout on each use of HttpURLConnection</para>
+ <para>* [JBREM-761] - NPE in BisocketServerInvoker$ControlConnectionThread</para>
+ <para>* [JBREM-766] - Guard against "spurious wakeup" from Thread.sleep()</para>
+ <para>* [JBREM-771] - MicroSocketClientInvoker can experience socket leaks</para>
+ <para>* [JBREM-774] - BisocketClientInvoker.replaceControlSocket() and handleDisconnect() should close control socket</para>
+ <para>* [JBREM-775] - MicroSocketClientInvoker.initPool() should omit pool from log message</para>
+ <para>* [JBREM-778] - BisocketServerInvoker.start() creates a new static Timer each time</para>
+ <para>* [JBREM-779] - BisocketClientInvoker should guard agains scheduling on an expired Timer, part 2</para>
+ <para>* [JBREM-784] - Use separate maps for control sockets and ordinary sockets in BisocketClientInvoker</para>
+ <para>* [JBREM-785] - BisocketClientInvoker.transport() inadvertently uses listenerId member variable</para>
+ <para>* [JBREM-787] - Move network i/o in BisocketClientInvoker constructor to handleConnect()</para>
+ <para>* [JBREM-788] - Access to BisocketClientInvoker static maps should be synchronized in handleDisconnect()</para>
+ <para>* [JBREM-790] - NPE in BisocketClientInvoker$PingTimerTask</para>
+ <para>* [JBREM-793] - Lease should synchronize access to client map</para>
+ <para>* [JBREM-794] - LeasePinger.addClient() should not create a new LeaseTimerTask if none currently exists</para>
+
+ <para>* The following is the public version of support patch JBREM-791, under which the fix was applied. -RS</para>
+ <para>* [JBREM-806] - In HTTPClientInvoker remove newlines and carriage returns from Base64 encoded user names and passwords</para>
+
+<para>** Feature Request</para>
+ <para>* [JBREM-749] - BisocketServerInvoker: Make configurable the address and port of secondary server socket</para>
+ <para>* [JBREM-755] - Make ConnectorValidator parameters configurable</para>
+ <para>* [JBREM-756] - CallbackPoller should shut down if too many errors occur.</para>
+ <para>* [JBREM-757] - Implement quick Client.removeListener() for polled callbacks.</para>
+ <para>* [JBREM-765] - Add a separate timeout parameter for callback clients</para>
+
+<para>** Patch</para>
+ <para>* [JBREM-781] - Socket transport needs to provide to the client local address of a TCP/IP connection, as seen from the server</para>
+
+
+<para>** Release</para>
+ <para>* [JBREM-789] - Release 2.2.2.GA</para>
+
+
+<para>** Task</para>
+ <para>* [JBREM-641] - re-implement the callback polling for http transport to reduce latency</para>
+ <para>* [JBREM-767] - Avoid deadlock in callback BisocketClientInvoker when timeout == 0</para>
+ <para>* [JBREM-782] - Remove network i/o from synch block in ServerInvokerCallbackHandler.getCallbackHandler()</para>
+ <para>* [JBREM-783] - Remove network i/o from synch blocks that establish and terminate LeasePingers</para>
+ <para>* [JBREM-796] - Verify Remoting 2.2.2 is compatible with earlier versions</para>
+
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.1.GA</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-751] - Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker</para>
+
+<para>** Release</para>
+ <para>* [JBREM-763] - Release 2.2.1.GA</para>
+<para>==========================================================================================================</para>
+<para>Release Notes - JBoss Remoting - Version 2.2.0.SP4</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-748] - BisocketClientInvoker should guard agains scheduling on an expired Timer</para>
+
+<para>** Release</para>
+ <para>* [JBREM-744] - Release 2.2.0.SP4</para>
+
+<para>** Task</para>
+ <para>* [JBREM-714] - Make sure 2.2.0 and 2.0.0 are compatible binary releases </para>
+ <para>* [JBREM-734] - BisocketClientInvoker constructor should get parameters from InvokerLocator as well as configuration map.</para>
+
+<para>========================================================================================================== </para>
+<para>Release Notes - JBoss Remoting - Version 2.2.0.SP3</para>
+
+<para>** Task</para>
+ <para>* [JBREM-741] - Eliminate unnecessary log.warn() in BisocketServerInvoker</para>
+
+<para>Release Notes - JBoss Remoting - Version 2.2.0.SP2</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-739] - Fix java serialization leak. [Note. This issue has been moved to 2.4.0.Beta1
+ pending the addition of unit tests, but the bug has been fixed.]</para>
+
+<para>Release Notes - JBoss Remoting - Version 2.2.0.SP1</para>
+
+<para>** Bug</para>
+ <para>* [JBREM-732] - When server terminates and has clients, when the server comes back up clients that survived, can't connect. Connection refused when trying to connect the control socket.</para>
+
+
<para>Release Notes - JBoss Remoting - Version 2.2.0.GA (Bluto) </para>
- <para>** Bug * [JBREM-721] - Fix memory leaks in bisocket transport and
+ <para><para>** Bug</para> * [JBREM-721] - Fix memory leaks in bisocket transport and
LeasePinger </para>
<para>* [JBREM-722] - BisocketClientInvoker should start pinging on control
@@ -45,7 +263,7 @@
<para>Release Notes - JBoss Remoting - Version 2.2.0.Beta1 (Bluto) </para>
- <para>** Bug * [JBREM-581] - can not do connection validation with ssl
+ <para><para>** Bug</para> * [JBREM-581] - can not do connection validation with ssl
transport (only impacts detection) </para>
<para>* [JBREM-600] -
@@ -194,7 +412,7 @@
<para>Release Notes - JBoss Remoting - Version 2.2.0.Alpha6 </para>
- <para>** Bug * [JBREM-662] - Failed ClientInvoker not cleaned up properly
+ <para><para>** Bug</para> * [JBREM-662] - Failed ClientInvoker not cleaned up properly
</para>
<para>* [JBREM-673] - Use of java.util.Timer recently added and not set to
@@ -220,7 +438,7 @@
<para>Release Notes - JBoss Remoting - Version 2.2.0.Alpha5</para>
- <para> ** Bug </para>
+ <para> <para>** Bug</para> </para>
<para>* [JBREM-666] - Broken or malicious clients can lock up the remoting
server </para>
@@ -233,14 +451,14 @@
<para>Release Notes - JBoss Remoting - Version 2.2.0.Alpha4 </para>
- <para>** Bug </para>
+ <para><para>** Bug</para> </para>
<para>* [JBREM-649] - Concurrent exceptions on Lease when
connecting/disconnecting new Clients </para>
<para>Release Notes - JBoss Remoting - Version 2.2.0.Alpha3 (Bluto) </para>
- <para>** Bug </para>
+ <para><para>** Bug</para> </para>
<para>* [JBREM-594] - invoker not torn down upon connector startup error
</para>
@@ -336,7 +554,7 @@
<para>Release Notes - JBoss Remoting - Version 2.0.0.GA (Boon)</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-568] - SSLSocketBuilderMBean does not have matching
getter/setter attribute types</para>
@@ -399,7 +617,7 @@
<para>Release Notes - JBoss Remoting - Version 2.0.0.CR1 (Boon)</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-303] -
org.jboss.test.remoting.transport.multiplex.BasicSocketTestCase(jboss_serialization)
@@ -636,7 +854,7 @@
<para>Release Notes - JBoss Remoting - Version 2.0.0.Beta2 (Boon)</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-304] -
org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)
@@ -817,7 +1035,7 @@
<para>Release Notes - JBoss Remoting - Version 2.0.0.Beta1</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-372] - memory leak on server side leasing</para>
@@ -838,7 +1056,7 @@
<para>Release Notes - JBoss Remoting - Version 1.4.4.GA</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-426] - keyStorePath and keyStorePassword being printed to
standard out</para>
@@ -847,7 +1065,7 @@
<para>Release Notes - JBoss Remoting - Version 1.4.3.GA</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-418] - ObjectInputStreamWithClassLoader can't handle
primitives</para>
@@ -872,7 +1090,7 @@
<para>* [JBREM-325] - move IMarshalledValue from jboss-commons to
jboss-remoting.jar</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-313] - client lease does not work if client and server in
same VM (using local invoker)</para>
@@ -968,7 +1186,7 @@
<para>* [JBREM-280] - no way to add path to invoker uri when using complex
configuration</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-41] - problem using localhost/127.0.0.1</para>
@@ -1118,7 +1336,7 @@
<para></para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-127] - RMI Invoker will not bind to specified address</para>
@@ -1187,7 +1405,7 @@
<para>* [JBREM-161] - Upgrade JRunit to Beta 2</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-147] - Invalid reuse of target location</para>
@@ -1245,7 +1463,7 @@
<para>* [JBREM-122] - need log4j.xml in examples</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-58] - Bug with multiple callback handler registered with same
server</para>
@@ -1341,7 +1559,7 @@
<para>Release Notes - JBoss Remoting - Version 1.0.2 final</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-36] - performance tests fail for http transports</para>
@@ -1370,7 +1588,7 @@
<para>* [JBREM-54] - Need access to HTTP response headers</para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-1] - Thread.currentThread().getContextClassLoader() is
wrong</para>
@@ -1412,7 +1630,7 @@
<para></para>
- <para>** Bug</para>
+ <para><para>** Bug</para></para>
<para>* [JBREM-19] - Try to reconnect on connection failure within socket
invoker</para>
More information about the jboss-remoting-commits
mailing list