[jboss-jira] [JBoss JIRA] Closed: (JBAS-7249) Upgrade Remoting to 2.5.2

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBAS-7249.
---------------------------

    Resolution: Done


Remoting release is now in the maven repository: http://anonsvn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/remoting/jboss-remoting/, and I've upgraded Remoting to 2.5.2 in component-matrix/pom.xml on Branch_5_x.

I ran tests-standard-unit with Remoting 2.5.1 and got 14 failures.  When I ran tests-standard-unit with Remoting 2.5.2 I got a proper subset with twelve failures, none of which seem to have anything to do with Remoting:

    [junit] Running org.jboss.test.aop.test.RemotingUnitTestCase
    [junit] Tests run: 4, Failures: 0, Errors: 2, Time elapsed: 11.344 sec
    
    [junit] Running org.jboss.test.ejb.lifecycle.test.BmpLifeCycleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
    
    [junit] Running org.jboss.test.jca.test.StatisticsFormatterUnitTestCase
    [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 2.219 sec
    
    [junit] Running org.jboss.test.jmx.test.HAInvokerUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.75 sec
    
    [junit] Running org.jboss.test.jmx.test.JBAS3050URLDeploymentScannerUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 25.094 sec
    
    [junit] Running org.jboss.test.jmx.test.SimpleURLDeploymentScannerUnitTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 9.89 sec
    
    [junit] Running org.jboss.test.jmx.test.XMLAttributePersistenceManagerUnitTestCase
    [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 2.344 sec
    
    [junit] Running org.jboss.test.naming.test.NamingRestartUnitTestCase
    [junit] Tests run: 12, Failures: 0, Errors: 12, Time elapsed: 9.141 sec
    
    [junit] Running org.jboss.test.naming.test.SimpleUnitTestCase
    [junit] Tests run: 10, Failures: 0, Errors: 5, Time elapsed: 16.843 sec
    
    [junit] Running org.jboss.test.xml.DynamicLoginConfigUnitTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 1.828 sec
    
    [junit] Running org.jboss.test.xml.SingletonSchemaBindingResolverUnitTestCase
    [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 0.375 sec
    
    [junit] Running org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.094 sec

> Upgrade Remoting to 2.5.2
> -------------------------
>
>                 Key: JBAS-7249
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7249
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: JBossAS-5.2.0.Beta1
>
>
> Release 2.5.2 should be compatible with 2.5.1, the version currently used in AS 5.
> Release Notes - JBoss Remoting - Version 2.5.2 (Flounder) - Text format
> Bug
>     * [JBREM-1077] - Fix problem in CompressingMarshaller
>     * [JBREM-1101] - Low: Missing header validation in org.jboss.remoting.transport.servlet.ServletServerInvoker
>     * [JBREM-1105] - DefaultLoadBalancer doesn't use all available server (if there are x servers available it uses x-1 of these)
>     * [JBREM-1121] - Client SocketFactory should be configurable by InvokerLocator
>     * [JBREM-1125] - Test for IllegalStateException when calling Timer.schedule()
>     * [JBREM-1133] - CLONE [JBREM-1129] - Eliminate nondeterminism in Lease updates
>     * [JBREM-1137] - New jnpserver requires wrapping call to new InitialContext() in PrivilegedExceptionAction
>     * [JBREM-1145] - HTTPUnMarshaller shouldn't use the value of content-type to determine the type of an object
>     * [JBREM-1147] - BisocketClientInvoker.createSocket() in callback mode should check for replaced control socket
>     * [JBREM-1150] - Lease should update client list if PING invocation has same time as previous PING
>     * [JBREM-1154] - Client.connect() should throw an exception when Lease creation fails
> Feature Request
>     * [JBREM-1102] - Make configuration map available to MarshalFactory
>     * [JBREM-1120] - Add a socket write timeout facility
>     * [JBREM-1123] - SocketServerInvoker needs an immediate shutdown option
>     * [JBREM-1124] - Invokers need option for configuration map parameters to override InvokerLocator parameters
>     * [JBREM-1132] - CLONE [JBREM-1128] - Introduce connection identity concept
>     * [JBREM-1139] - Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
>     * [JBREM-1146] - Treat IOException("Connection reset by peer") as a retriable exception
> Release
>     * [JBREM-1135] - Release 2.5.2
> Task
>     * [JBREM-1134] - Assure version compatibility with earlier versions of Remoting
>     * [JBREM-1136] - Update jars to match AS 5.1.0
>     * [JBREM-1142] - Clarify use of "clientConnectAddress" in RemotingGuide
>     * [JBREM-1151] - Correct dependency discussion in Chapter 4 of Remoting Guide
>     * [JBREM-1155] - Assure version compatibility with earlier versions of Remoting

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira