Test failures with JGDMS
11 views
Skip to first unread message
Peter Firmstone
Jun 19, 2017, 3:44:22 AM6/19/17
to Rio Users Group
I'm getting the following three test failures when testing against a modular maven fork of River 3.0 (JGDMS), after adjusting dependencies in pom files, it appears to be related to RIO_HOME not being set.
I set the RIO_HOME environment variable to the root directory of the distribution. Testing was performed on Windows 7, I haven't tested on Linux yet.
I'm also using a compatibility layer library for the com.sun.jini namespace for River / Jini 2.X and haven't changed any package imports in Rio.
Any ideas?
Thanks,
Peter.
[INFO] ------------------------------------------------------------------------
[INFO] Building Module :: Monitor Service Implementation 5.2.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ monitor-service ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ monitor-service ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ monitor-service ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ monitor-service ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ monitor-service ---
[INFO] Surefire report directory: C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.rioproject.monitor.service.channel.ServiceChannelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.414 sec
Running org.rioproject.monitor.service.DefaultOpStringManagerTest
13:13:58.747 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],6264c47a-e
cd1-4579-b374-44f9dfae6554]
13:13:58.938 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:13:58.946 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-1] active [false]
13:13:59.128 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-1] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],fe36729d
-0007-4ab1-872a-e5d7e6516b86]
13:13:59.130 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-1 standAlone: true
===> getOperationalStringManager
13:13:59.136 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-2] active [false]
13:13:59.313 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-2] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],70be58a0
-5d95-4375-a0a6-08a96fb2cb22]
13:13:59.314 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-2 standAlone: false
===> getOperationalStringManager
13:13:59.315 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-2]
13:13:59.316 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-2] terminated
13:13:59.317 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-2] active [false]
13:13:59.497 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-2] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],729889b4
-a83d-4f6e-9a50-3335082605a4]
13:13:59.499 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-2 standAlone: false
===> getOperationalStringManager
13:13:59.500 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-1] active [false]
13:13:59.681 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-1] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],24695265
-12be-449c-b3bc-fea7c9cbdd19]
13:13:59.682 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-1 standAlone: false
===> getOperationalStringManager
13:13:59.683 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-2]
13:13:59.683 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-1]
13:13:59.683 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-1] terminated
13:13:59.684 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-2] terminated
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.284 sec
Running org.rioproject.monitor.service.managers.IdleServiceManagerTest
13:13:59.696 [main] DEBUG o.r.m.s.managers.IdleServiceManager - Service [foo/bar] idle time: 3 seconds, computed delay time for checking idle status: 1 second.
13:14:01.201 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:02.703 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:04.205 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 1 / 2 idle instances. Next check in 1 second.
13:14:05.706 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 2 / 2 idle instances. Notify for undeploy.
Waited 4501 millis
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.516 sec
Running org.rioproject.monitor.service.OpStringManagerControllerTest
concurrentCreationTest
----------------------
13:14:06.215 [Thread-1] INFO o.r.m.s.OpStringManagerController - Adding OpString [concurrent] active [false]
Created 100 threads to bang on one OpStringManagerController
13:14:06.414 [Thread-1] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [concurrent] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],
bcb7a5f4-8ab3-41b0-97bb-01761e81e658]
13:14:06.416 [Thread-1] DEBUG o.r.m.service.DefaultOpStringManager - Manager for concurrent standAlone: true
===> getOperationalStringManager
13:14:06.878 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test] active [true]
13:14:07.053 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],22e93b44-8
cd0-425f-8b3c-28343e177432]
13:14:07.055 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:14:07.086 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new DiscoveryManagementPool
13:14:07.095 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new DiscoveryControl for [test]
13:14:07.095 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new SharedDiscoveryManager for groups [], shared name [test], using null config
13:14:07.207 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:08.708 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:10.209 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:11.726 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:13.227 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:13.517 [main] DEBUG org.rioproject.monitor.services - ServiceElementManager.verify(): [test/foo] actual [0], pending [0], maintain [1]
13:14:13.529 [main] WARN o.r.m.service.ServiceProvisioner - Failure Reason(s):
1: There are no registered Cybernodes, unable to provision foo
13:14:13.531 [main] DEBUG o.r.m.service.ServiceProvisioner - Wrote [test/foo] to Dynamic-Service TestManager
13:14:13.537 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test]
13:14:13.538 [main] DEBUG o.r.m.s.m.PendingServiceElementManager - Dynamic-Service TestManager: removing [1] [test/foo] instances
13:14:13.538 [main] DEBUG org.rioproject.monitor.services - Terminating [0] instances of [test/foo] ...
13:14:13.538 [main] DEBUG org.rioproject.monitor.services - Completed [test/foo] service termination
13:14:13.539 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test] terminated
13:14:13.539 [main] INFO o.r.m.s.OpStringManagerController - Undeployed Operational String [test]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.331 sec
===> fire
13:14:14.728 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:16.229 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.3:jar (default-jar) @ monitor-service ---
[INFO]
[INFO] --- maven-shade-plugin:1.4:shade (default) @ monitor-service ---
[INFO] Excluding org.rioproject:rio-lib:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-platform:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-logging-support:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-api:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-ui-factory:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-proxy:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-lib:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-platform:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding com.boundary:high-scale-lib:jar:1.0.6 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-collections:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding biz.aQute.bnd:biz.aQute.bnd.annotation:jar:3.3.0 from the shaded jar.
[INFO] Excluding org.osgi:org.osgi.core:jar:4.1.0 from the shaded jar.
[INFO] Excluding org.osgi:org.osgi.util.tracker:jar:1.5.1 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-discovery-providers:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-resources:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.codehaus.groovy:groovy-all:jar:2.3.8 from the shaded jar.
[INFO] Including org.rioproject.monitor:monitor-api:jar:5.2.3-SNAPSHOT in the shaded jar.
[INFO] Including org.rioproject.monitor:monitor-proxy:jar:5.2.3-SNAPSHOT in the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-lib-dl:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-url-integrity:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-jeri:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.slf4j:slf4j-api:jar:1.7.12 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:service-starter:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-pref-class-loader:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jini-2.1-compat:jar:3.0-SNAPSHOT from the shaded jar.
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionFailureEvent.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitor$PeerInfo.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\riopr
oject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitor.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioproject\mon
itor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorAdmin.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorEvent$Action.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\ri
oproject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorEvent.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ServiceProvisionEventHandler.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\ri
oproject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$1.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\
org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$ConstrainableProvisionMonitorAdminProxy.class in C:\Users\peter\Documents\
NetBeansProjects\Rio\target\test-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$Verifier.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\tes
t-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\or
g\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorPermission.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\or
g\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$1.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\r
ioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$ConstrainableProvisionMonitorProxy.class in C:\Users\peter\Documents\NetBeansPr
ojects\Rio\target\test-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$Verifier.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-rep
o\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rio
project\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\monitor-service-5.2.3-SNAPSHOT.jar with C:\Users\pete
r\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\monitor-service-5.2.3-SNAPSHOT-shaded.jar
[INFO]
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (default) @ monitor-service ---
[INFO] Failsafe report directory: C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\failsafe-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.rioproject.monitor.service.DeploymentVerifierTest
Jun 19, 2017 1:14:42 PM org.apache.river.reggie.RegistrarImpl$Unicast <init>
INFO: Reggie Unicast Discovery listening on port 4,160
Jun 19, 2017 1:14:59 PM org.apache.river.reggie.RegistrarImpl destroy
INFO: starting Reggie shutdown
Exception in thread "destroy" java.lang.IllegalStateException: no object exported via this exporter
at net.jini.jeri.BasicJeriExporter.unexport(BasicJeriExporter.java:661)
at org.apache.river.reggie.RegistrarImpl$Destroy.run(RegistrarImpl.java:2641)
at java.lang.Thread.run(Thread.java:744)
Jun 19, 2017 1:15:24 PM org.apache.river.reggie.RegistrarImpl$Unicast <init>
INFO: Reggie Unicast Discovery listening on port 4,160
Jun 19, 2017 1:15:52 PM org.apache.river.reggie.RegistrarImpl destroy
INFO: starting Reggie shutdown
Exception in thread "destroy" java.lang.IllegalStateException: no object exported via this exporter
at net.jini.jeri.BasicJeriExporter.unexport(BasicJeriExporter.java:661)
at org.apache.river.reggie.RegistrarImpl$Destroy.run(RegistrarImpl.java:2641)
at java.lang.Thread.run(Thread.java:744)
Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 90.549 sec <<< FAILURE! - in org.rioproject.monitor.service.DeploymentVerifierTest
testEnsureMultiGroups(org.rioproject.monitor.service.DeploymentVerifierTest) Time elapsed: 29.766 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.rioproject.monitor.service.DeploymentVerifierTest.testEnsureMultiGroups(DeploymentVerifierTest.java:137)
testEnsureGroups(org.rioproject.monitor.service.DeploymentVerifierTest) Time elapsed: 45.62 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.rioproject.monitor.service.DeploymentVerifierTest.testEnsureGroups(DeploymentVerifierTest.java:125)
Running org.rioproject.monitor.service.InstantiatorResourceTest
13:15:54.156 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:54.933 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],dd367c1c-a
42c-4178-9d43-1e2ce6b47199]
13:15:55.216 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:55.925 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:56.147 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],83c60fa8-a
cdf-4780-aa95-0a5c68f61d3e]
13:15:56.148 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:56.156 [main] WARN o.r.m.service.InstantiatorResource - The operating systems being requested [ES/390, Ubuntu] are not supported by the target resource's
operating system [Windows 7] for [test/foo]
13:15:57.096 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:57.551 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],daba8b14-d
fbb-4cb2-88bf-57a922bae58d]
13:15:57.697 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:57.782 [main] WARN o.r.m.service.InstantiatorResource - The target resource's machine name/ip [medusa/10.92.41.161] is on the exclusion list of [10.92.41
.161, 192.168.1.9] for [test/foo]
13:15:57.782 [main] DEBUG o.r.m.service.InstantiatorResource - test does not meet requirements for DYNAMIC service [test/foo]
13:15:57.783 [main] WARN o.r.m.service.InstantiatorResource - test does not meet requirements for DYNAMIC service [test/foo] [Name: Network, {Address=10.92.41.
161}, Exclude: true], [Name: Network, {Address=192.168.1.9}, Exclude: true]
13:15:58.825 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:59.313 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],7f3968ac-6
308-49f7-8ae6-0d43b9ad5985]
13:15:59.314 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:00.283 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:00.940 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],9b4b38f0-8
5df-4360-8fff-137bed36f24b]
13:16:00.941 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:02.119 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:02.491 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],b440b4eb-6
894-4922-86ed-1d764e781f88]
13:16:02.493 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:02.495 [main] WARN o.r.m.service.InstantiatorResource - The operating systems being requested [Mac OS X, Windows, Linux] are not supported by the target
resource's operating system [Windows 7] for [test/foo]
13:16:03.062 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:03.255 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],609fbab9-6
28b-499e-b55c-19a09ff4f278]
13:16:03.262 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:03.263 [main] WARN o.r.m.service.InstantiatorResource - The target resource's machine name/ip [medusa/10.92.41.161] is on the exclusion list of [10.92.41
.161] for [test/foo]
13:16:03.629 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:03.808 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],0d72a6a1-2
724-4007-89b8-6295ea87716f]
13:16:03.809 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:03.810 [main] DEBUG o.r.m.service.InstantiatorResource - test meets qualitative requirements for [test/foo]
13:16:04.144 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:04.315 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],37cdd75b-2
ab8-420d-a13c-f5a9e1c97b55]
13:16:04.317 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:04.318 [main] WARN o.r.m.service.InstantiatorResource - The architectures being requested [sparc, amd] are not supported by the target resource's archite
cture [x86] for [test/foo]
13:16:04.718 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:04.887 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],da9b0c60-4
552-4d2b-954d-3727fc15a91b]
13:16:04.889 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.353 sec <<< FAILURE! - in org.rioproject.monitor.service.InstantiatorResourceTest
testMeetsQualitativeRequirements(org.rioproject.monitor.service.InstantiatorResourceTest) Time elapsed: 1.537 sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<3>
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:142)
Results :
Failed tests:
DeploymentVerifierTest.testEnsureGroups:125 null
DeploymentVerifierTest.testEnsureMultiGroups:137 null
InstantiatorResourceTest.testMeetsQualitativeRequirements:142 expected:<0> but was:<3>
Tests run: 14, Failures: 3, Errors: 0, Skipped: 0
I set the RIO_HOME environment variable to the root directory of the distribution. Testing was performed on Windows 7, I haven't tested on Linux yet.
I'm also using a compatibility layer library for the com.sun.jini namespace for River / Jini 2.X and haven't changed any package imports in Rio.
Any ideas?
Thanks,
Peter.
[INFO] ------------------------------------------------------------------------
[INFO] Building Module :: Monitor Service Implementation 5.2.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ monitor-service ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ monitor-service ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ monitor-service ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ monitor-service ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ monitor-service ---
[INFO] Surefire report directory: C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.rioproject.monitor.service.channel.ServiceChannelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.414 sec
Running org.rioproject.monitor.service.DefaultOpStringManagerTest
13:13:58.747 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],6264c47a-e
cd1-4579-b374-44f9dfae6554]
13:13:58.938 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:13:58.946 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-1] active [false]
13:13:59.128 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-1] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],fe36729d
-0007-4ab1-872a-e5d7e6516b86]
13:13:59.130 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-1 standAlone: true
===> getOperationalStringManager
13:13:59.136 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-2] active [false]
13:13:59.313 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-2] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],70be58a0
-5d95-4375-a0a6-08a96fb2cb22]
13:13:59.314 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-2 standAlone: false
===> getOperationalStringManager
13:13:59.315 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-2]
13:13:59.316 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-2] terminated
13:13:59.317 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-2] active [false]
13:13:59.497 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-2] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],729889b4
-a83d-4f6e-9a50-3335082605a4]
13:13:59.499 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-2 standAlone: false
===> getOperationalStringManager
13:13:59.500 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test-1] active [false]
13:13:59.681 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test-1] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],24695265
-12be-449c-b3bc-fea7c9cbdd19]
13:13:59.682 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test-1 standAlone: false
===> getOperationalStringManager
13:13:59.683 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-2]
13:13:59.683 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test-1]
13:13:59.683 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-1] terminated
13:13:59.684 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test-2] terminated
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.284 sec
Running org.rioproject.monitor.service.managers.IdleServiceManagerTest
13:13:59.696 [main] DEBUG o.r.m.s.managers.IdleServiceManager - Service [foo/bar] idle time: 3 seconds, computed delay time for checking idle status: 1 second.
13:14:01.201 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:02.703 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:04.205 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 1 / 2 idle instances. Next check in 1 second.
13:14:05.706 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 2 / 2 idle instances. Notify for undeploy.
Waited 4501 millis
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.516 sec
Running org.rioproject.monitor.service.OpStringManagerControllerTest
concurrentCreationTest
----------------------
13:14:06.215 [Thread-1] INFO o.r.m.s.OpStringManagerController - Adding OpString [concurrent] active [false]
Created 100 threads to bang on one OpStringManagerController
13:14:06.414 [Thread-1] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [concurrent] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],
bcb7a5f4-8ab3-41b0-97bb-01761e81e658]
13:14:06.416 [Thread-1] DEBUG o.r.m.service.DefaultOpStringManager - Manager for concurrent standAlone: true
===> getOperationalStringManager
13:14:06.878 [main] INFO o.r.m.s.OpStringManagerController - Adding OpString [test] active [true]
13:14:07.053 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],22e93b44-8
cd0-425f-8b3c-28343e177432]
13:14:07.055 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:14:07.086 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new DiscoveryManagementPool
13:14:07.095 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new DiscoveryControl for [test]
13:14:07.095 [main] DEBUG o.r.i.client.DiscoveryManagementPool - Create new SharedDiscoveryManager for groups [], shared name [test], using null config
13:14:07.207 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:08.708 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:10.209 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:11.726 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:13.227 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:13.517 [main] DEBUG org.rioproject.monitor.services - ServiceElementManager.verify(): [test/foo] actual [0], pending [0], maintain [1]
13:14:13.529 [main] WARN o.r.m.service.ServiceProvisioner - Failure Reason(s):
1: There are no registered Cybernodes, unable to provision foo
13:14:13.531 [main] DEBUG o.r.m.service.ServiceProvisioner - Wrote [test/foo] to Dynamic-Service TestManager
13:14:13.537 [main] DEBUG o.r.m.service.DefaultOpStringManager - Removed [test]
13:14:13.538 [main] DEBUG o.r.m.s.m.PendingServiceElementManager - Dynamic-Service TestManager: removing [1] [test/foo] instances
13:14:13.538 [main] DEBUG org.rioproject.monitor.services - Terminating [0] instances of [test/foo] ...
13:14:13.538 [main] DEBUG org.rioproject.monitor.services - Completed [test/foo] service termination
13:14:13.539 [main] INFO o.r.m.service.DefaultOpStringManager - OpStringManager [test] terminated
13:14:13.539 [main] INFO o.r.m.s.OpStringManagerController - Undeployed Operational String [test]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.331 sec
===> fire
13:14:14.728 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
13:14:16.229 [pool-1-thread-1] INFO o.r.m.s.managers.IdleServiceManager - Service [foo/bar] has 0 / 2 idle instances. Next check in 1 second.
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.3:jar (default-jar) @ monitor-service ---
[INFO]
[INFO] --- maven-shade-plugin:1.4:shade (default) @ monitor-service ---
[INFO] Excluding org.rioproject:rio-lib:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-platform:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-logging-support:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-api:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-ui-factory:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.rioproject:rio-proxy:jar:5.2.3-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-lib:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-platform:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding com.boundary:high-scale-lib:jar:1.0.6 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-collections:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding biz.aQute.bnd:biz.aQute.bnd.annotation:jar:3.3.0 from the shaded jar.
[INFO] Excluding org.osgi:org.osgi.core:jar:4.1.0 from the shaded jar.
[INFO] Excluding org.osgi:org.osgi.util.tracker:jar:1.5.1 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-discovery-providers:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-resources:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.codehaus.groovy:groovy-all:jar:2.3.8 from the shaded jar.
[INFO] Including org.rioproject.monitor:monitor-api:jar:5.2.3-SNAPSHOT in the shaded jar.
[INFO] Including org.rioproject.monitor:monitor-proxy:jar:5.2.3-SNAPSHOT in the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-lib-dl:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-url-integrity:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-jeri:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding org.slf4j:slf4j-api:jar:1.7.12 from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:service-starter:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jgdms-pref-class-loader:jar:3.0-SNAPSHOT from the shaded jar.
[INFO] Excluding au.net.zeus.jgdms:jini-2.1-compat:jar:3.0-SNAPSHOT from the shaded jar.
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionFailureEvent.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitor$PeerInfo.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\riopr
oject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitor.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioproject\mon
itor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorAdmin.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorEvent$Action.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\ri
oproject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ProvisionMonitorEvent.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rioprojec
t\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/ServiceProvisionEventHandler.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\ri
oproject\monitor\monitor-api\5.2.3-SNAPSHOT\monitor-api-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$1.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\
org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$ConstrainableProvisionMonitorAdminProxy.class in C:\Users\peter\Documents\
NetBeansProjects\Rio\target\test-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy$Verifier.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\tes
t-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorAdminProxy.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\or
g\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorPermission.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\or
g\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$1.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\r
ioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$ConstrainableProvisionMonitorProxy.class in C:\Users\peter\Documents\NetBeansPr
ojects\Rio\target\test-repo\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy$Verifier.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-rep
o\org\rioproject\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[WARNING] We have a duplicate org/rioproject/monitor/proxy/ProvisionMonitorProxy.class in C:\Users\peter\Documents\NetBeansProjects\Rio\target\test-repo\org\rio
project\monitor\monitor-proxy\5.2.3-SNAPSHOT\monitor-proxy-5.2.3-SNAPSHOT.jar
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\monitor-service-5.2.3-SNAPSHOT.jar with C:\Users\pete
r\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\monitor-service-5.2.3-SNAPSHOT-shaded.jar
[INFO]
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (default) @ monitor-service ---
[INFO] Failsafe report directory: C:\Users\peter\Documents\NetBeansProjects\Rio\rio-services\monitor\monitor-service\target\failsafe-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.rioproject.monitor.service.DeploymentVerifierTest
Jun 19, 2017 1:14:42 PM org.apache.river.reggie.RegistrarImpl$Unicast <init>
INFO: Reggie Unicast Discovery listening on port 4,160
Jun 19, 2017 1:14:59 PM org.apache.river.reggie.RegistrarImpl destroy
INFO: starting Reggie shutdown
Exception in thread "destroy" java.lang.IllegalStateException: no object exported via this exporter
at net.jini.jeri.BasicJeriExporter.unexport(BasicJeriExporter.java:661)
at org.apache.river.reggie.RegistrarImpl$Destroy.run(RegistrarImpl.java:2641)
at java.lang.Thread.run(Thread.java:744)
Jun 19, 2017 1:15:24 PM org.apache.river.reggie.RegistrarImpl$Unicast <init>
INFO: Reggie Unicast Discovery listening on port 4,160
Jun 19, 2017 1:15:52 PM org.apache.river.reggie.RegistrarImpl destroy
INFO: starting Reggie shutdown
Exception in thread "destroy" java.lang.IllegalStateException: no object exported via this exporter
at net.jini.jeri.BasicJeriExporter.unexport(BasicJeriExporter.java:661)
at org.apache.river.reggie.RegistrarImpl$Destroy.run(RegistrarImpl.java:2641)
at java.lang.Thread.run(Thread.java:744)
Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 90.549 sec <<< FAILURE! - in org.rioproject.monitor.service.DeploymentVerifierTest
testEnsureMultiGroups(org.rioproject.monitor.service.DeploymentVerifierTest) Time elapsed: 29.766 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.rioproject.monitor.service.DeploymentVerifierTest.testEnsureMultiGroups(DeploymentVerifierTest.java:137)
testEnsureGroups(org.rioproject.monitor.service.DeploymentVerifierTest) Time elapsed: 45.62 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.rioproject.monitor.service.DeploymentVerifierTest.testEnsureGroups(DeploymentVerifierTest.java:125)
Running org.rioproject.monitor.service.InstantiatorResourceTest
13:15:54.156 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:54.933 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],dd367c1c-a
42c-4178-9d43-1e2ce6b47199]
13:15:55.216 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:55.925 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:56.147 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],83c60fa8-a
cdf-4780-aa95-0a5c68f61d3e]
13:15:56.148 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:56.156 [main] WARN o.r.m.service.InstantiatorResource - The operating systems being requested [ES/390, Ubuntu] are not supported by the target resource's
operating system [Windows 7] for [test/foo]
13:15:57.096 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:57.551 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],daba8b14-d
fbb-4cb2-88bf-57a922bae58d]
13:15:57.697 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:15:57.782 [main] WARN o.r.m.service.InstantiatorResource - The target resource's machine name/ip [medusa/10.92.41.161] is on the exclusion list of [10.92.41
.161, 192.168.1.9] for [test/foo]
13:15:57.782 [main] DEBUG o.r.m.service.InstantiatorResource - test does not meet requirements for DYNAMIC service [test/foo]
13:15:57.783 [main] WARN o.r.m.service.InstantiatorResource - test does not meet requirements for DYNAMIC service [test/foo] [Name: Network, {Address=10.92.41.
161}, Exclude: true], [Name: Network, {Address=192.168.1.9}, Exclude: true]
13:15:58.825 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:15:59.313 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],7f3968ac-6
308-49f7-8ae6-0d43b9ad5985]
13:15:59.314 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:00.283 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:00.940 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],9b4b38f0-8
5df-4360-8fff-137bed36f24b]
13:16:00.941 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:02.119 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:02.491 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],b440b4eb-6
894-4922-86ed-1d764e781f88]
13:16:02.493 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:02.495 [main] WARN o.r.m.service.InstantiatorResource - The operating systems being requested [Mac OS X, Windows, Linux] are not supported by the target
resource's operating system [Windows 7] for [test/foo]
13:16:03.062 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:03.255 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],609fbab9-6
28b-499e-b55c-19a09ff4f278]
13:16:03.262 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:03.263 [main] WARN o.r.m.service.InstantiatorResource - The target resource's machine name/ip [medusa/10.92.41.161] is on the exclusion list of [10.92.41
.161] for [test/foo]
13:16:03.629 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:03.808 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],0d72a6a1-2
724-4007-89b8-6295ea87716f]
13:16:03.809 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:03.810 [main] DEBUG o.r.m.service.InstantiatorResource - test meets qualitative requirements for [test/foo]
13:16:04.144 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:04.315 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],37cdd75b-2
ab8-420d-a13c-f5a9e1c97b55]
13:16:04.317 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
13:16:04.318 [main] WARN o.r.m.service.InstantiatorResource - The architectures being requested [sparc, amd] are not supported by the target resource's archite
cture [x86] for [test/foo]
13:16:04.718 [main] WARN org.rioproject.system - Unable to establish the platform configuration directory, most likely RIO_HOME is not set.
13:16:04.887 [main] DEBUG o.r.m.service.DefaultOpStringManager - Deployment [test] using exporter BasicJeriExporter[TcpServerEndpoint[10.92.41.161:0],da9b0c60-4
552-4d2b-954d-3727fc15a91b]
13:16:04.889 [main] DEBUG o.r.m.service.DefaultOpStringManager - Manager for test standAlone: true
Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.353 sec <<< FAILURE! - in org.rioproject.monitor.service.InstantiatorResourceTest
testMeetsQualitativeRequirements(org.rioproject.monitor.service.InstantiatorResourceTest) Time elapsed: 1.537 sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<3>
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:142)
Results :
Failed tests:
DeploymentVerifierTest.testEnsureGroups:125 null
DeploymentVerifierTest.testEnsureMultiGroups:137 null
InstantiatorResourceTest.testMeetsQualitativeRequirements:142 expected:<0> but was:<3>
Tests run: 14, Failures: 3, Errors: 0, Skipped: 0
Dennis Reedy
Jun 19, 2017, 8:02:00 AM6/19/17
to rio-...@googlegroups.com
Hi Peter,
How can I get the River distribution?
Dennis
--
You received this message because you are subscribed to the Google Groups "Rio Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rio-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dennis Reedy
Jun 23, 2017, 11:40:03 AM6/23/17
to rio-...@googlegroups.com
Hi Peter,
I've built the JGDMS project, what are the mods to Rio that you made in order to use the compatibility jars for River?
Thanks
Dennis
Peter Firmstone
May 12, 2018, 8:19:02 PM5/12/18
to Rio Users Group
Hi Dennis,
Apologies for my late reply, only pom dependencies require changing. The changes I made are obsolete now, but are available in the fork of Rio I made here: https://github.com/pfirmstone/Rio
Regards,
Peter.
To unsubscribe from this group and stop receiving emails from it, send an email to rio-users+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages