[
https://jira.jboss.org/browse/JBAS-8166?page=com.atlassian.jira.plugin.sy...
]
Ron Sigal resolved JBAS-8166.
-----------------------------
Resolution: Done
The hudson run JBoss-AS-6.0.x-testSuite-sun16 (Build #801 (Jul 15, 2010 2:26:27 AM) ran
with Remoting 2.5.3. There are three failures that didn't occur in the previous run
that went to completion:
*
org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionCountUnitTestCase(Default-udp).testMarshalledRedeployWarAndCache
*
org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase(profileservice).testSlsbLocal
* org.jboss.test.xml.DDValidatorUnitTestCase.testJBossXml
They don't appear to have any relationship to Remoting, so I'm closing the case.
Upgrade to Remoting 2.5.3
-------------------------
Key: JBAS-8166
URL:
https://jira.jboss.org/browse/JBAS-8166
Project: JBoss Application Server
Issue Type: Component Upgrade
Security Level: Public(Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 6.0.0.M4
Remoting 2.5.3 is a last minute release for EAP 5.1 with a security fix, JBREM-1231 -
"InvokerRegistry needs to have security checks for the setters". The security
fix is the only substantive change from release 2.5.2.SP3:
============================================================
Release Notes - JBoss Remoting - Version 2.5.3 (Flounder)
Bug
* [JBREM-1231] - InvokerRegistry needs to have security checks for the setters
Release
* [JBREM-1233] - Release 2.5.3
Task
* [JBREM-1219] - Update remoting guide for "generalizeSocketException"
* [JBREM-1229] - Display recreated InvokerLocator when bind address is 0.0.0.0
* [JBREM-1232] - Assure version compatibility with earlier versions of Remoting
============================================================
Testing:
* Smoke test passes with 2.5.3.
* I can't run the entire test suite to completion with either 2.5.2.SP3 or 2.5.3 (a
clustering test complains about a port in use), but I get essentially the same results for
both releases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira