Changes to Rio, to use the latest release of JGDMS 3.1.0 Jini Platfor… #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…m implementation.
|
Note this will add support for IPv6 Multicast discovery and TSLv1.2 JERI Endpoints to Rio. Performance is significantly enhanced over the Jini / River 2.x series releases. Only hot-spots are java sockets now and scalability and throughput have also improved. Hoping to get this out there so it will have more acceptance for inclusion into River. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…m implementation.
I am getting two test failures, however they seem unrelated to JGDMS, otherwise everything is building as expected using the Jini 2.1 compatibility library, which provides a com.sun.jini compatibility layer.
Test set: org.rioproject.monitor.service.InstantiatorResourceTest
Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.793 sec <<< FAILURE! - in org.rioproject.monitor.service.InstantiatorResourceTest
testMeetsQualitativeRequirements(org.rioproject.monitor.service.InstantiatorResourceTest) Time elapsed: 0.249 sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<2>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.rioproject.monitor.service.InstantiatorResourceTest.testMeetsQualitativeRequirements(InstantiatorResourceTest.java:145)
Test set: org.rioproject.resolver.LatestVersionTest
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.581 sec <<< FAILURE!
testLatestLocation(org.rioproject.resolver.LatestVersionTest) Time elapsed: 1.684 sec <<< ERROR!
org.rioproject.resolver.ResolverException: Error locating org.codehaus.groovy:groovy-all:LATEST: Could not find artifact org.codehaus.groovy:groovy-all:jar:3.0.0-beta-3 in rio (http://www.rio-project.org/maven2)
at org.rioproject.resolver.aether.AetherResolver.getLocation(AetherResolver.java:147)
at org.rioproject.resolver.LatestVersionTest.testLatestLocation(LatestVersionTest.java:66)