[jboss-jira] [JBoss JIRA] Updated: (JBAS-9043) Upgrade to Remoting 2.5.4.SP1
Shelly McGowan (JIRA)
jira-events at lists.jboss.org
Sat Apr 30 09:05:18 EDT 2011
[ https://issues.jboss.org/browse/JBAS-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shelly McGowan updated JBAS-9043:
---------------------------------
Assignee: Shelly McGowan
> Upgrade to Remoting 2.5.4.SP1
> -----------------------------
>
> Key: JBAS-9043
> URL: https://issues.jboss.org/browse/JBAS-9043
> Project: Legacy JBoss Application Server 6
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Ron Sigal
> Assignee: Shelly McGowan
> Fix For: 6.1.0
>
>
> Includes:
> ==========================================================================================================
> Release Notes - JBoss Remoting - Version 2.5.3.SP1
> Quality Risk
> * [JBREM-1234] - Avoid excessive calls to InetAddress.getLocalHost()
> Release
> * [JBREM-1237] - Release 2.5.3.SP1
> Task
> * [JBREM-1236] - Assure version compatibility with earlier versions of Remoting
> ==========================================================================================================
> Release Notes - JBoss Remoting - Version 2.5.4
> Bug
> * [JBREM-1226] - Sockets created by bisocket secondary ServerSocket should be configured properly
> * [JBREM-1227] - Fix deadlock between MicroRemoteClientInvoker and RemotingClassLoader
> * [JBREM-1242] - Fix deadlock between Client and MicroRemoteClientInvoker
> * [JBREM-1247] - BisocketClientInvoker$PingTimerTask NPE
> * [JBREM-1261] - Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread
> * [JBREM-1268] - RemoteClientInvoker can change configuration map and prevent InvokerRegistry from reusing client invokers
> * [JBREM-1269] - Fix deadlock between Client and MicroRemoteClientInvoker, part 2
> Enhancement
> * [JBREM-1238] - Need invocation timeouts in synchronized blocks in MicroRemoteClientInvoker that create and terminate leases
> * [JBREM-1245] - Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable
> * [JBREM-1246] - Can't authenticate using TransporterClient
> * [JBREM-1248] - Avoid connecting to a server in catch clause in case of HttpClientInvoker connection failure
> * [JBREM-1262] - Consider java.io.IOException("Software caused connection abort: socket write error") retriable
> * [JBREM-1263] - ClientSocketWrapper.checkConnection() should check returned value
> * [JBREM-1267] - Allow HTTPClientInvoker to call disconnect on HttpURLConnection after use
> Feature Request
> * [JBREM-1144] - Extend connection identity to server side
> Release
> * [JBREM-1271] - Release 2.5.4
> Task
> * [JBREM-1266] - Create Remoting users guide
> * [JBREM-1270] - Assure version compatibility with earlier versions of Remoting
> ==========================================================================================================
> Release Notes - JBoss Remoting - Version 2.5.4.SP1 - HTML format
> Bug
> * [JBREM-1261] - Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread
> Release
> * [JBREM-1274] - Release 2.5.4.SP1
> Task
> * [JBREM-1272] - Remove JBoss.ORG EULA file
> * [JBREM-1273] - Assure version compatibility with earlier versions of Remoting
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list