Rio 5.1.4 Calculator Example mvn rio:start-all does nothing
23 views
Skip to first unread message
pubu...@gmail.com
May 6, 2015, 5:40:22 AM5/6/15
to rio-...@googlegroups.com
Hi All,
I am trying out the calculator example.
Using RIO version 5.1.4
JDK version j1.7.0_79
Maven version 3.3.3
on Ubuntu 14.04
When running the mvn rio:start-all command from the calculator directory it gives a build success message as follows.
rio-5.1.4/examples/calculator$ mvn rio:start-all
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Example :: Calculator
[INFO] Example :: Calculator API
[INFO] Example :: Calculator Service Implementation
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator API 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator-api ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator Service Implementation 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator-service ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Example :: Calculator .............................. SUCCESS [ 0.295 s]
[INFO] Example :: Calculator API .......................... SUCCESS [ 0.002 s]
[INFO] Example :: Calculator Service Implementation ....... SUCCESS [ 0.001 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.893 s
[INFO] Finished at: 2015-05-06T15:05:25+05:30
[INFO] Final Memory: 11M/239M
[INFO] ------------------------------------------------------------------------
is this the expected output or should some applications start up as a result of this command?
Next when I run the mvn rio:deploy command from the command line the following is the output.
rio/rio-5.1.4/examples/calculator$ mvn rio:deploy
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Example :: Calculator
[INFO] Example :: Calculator API
[INFO] Example :: Calculator Service Implementation
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator ---
total 0
discovery time 5005 millis, timeout used 5000
No Provision Monitor instances discovered
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator API 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator-api ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator Service Implementation 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator-service ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Example :: Calculator .............................. SUCCESS [ 7.931 s]
[INFO] Example :: Calculator API .......................... SUCCESS [ 0.002 s]
[INFO] Example :: Calculator Service Implementation ....... SUCCESS [ 0.001 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.504 s
[INFO] Finished at: 2015-05-06T15:06:52+05:30
[INFO] Final Memory: 8M/239M
[INFO] ------------------------------------------------------------------------
mvn rio:ui gives the ui with "waiting to discovery the Rio system".
When I run rio from the command line following is the output
./bin/rio start all
INFO 15:08:57 starter config [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/start-all.groovy]
INFO 15:08:59.447 org.rioproject.config.RioProperties - /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/rio.env not found, skipping
WARN 15:08:59.788 org.rioproject.start - service.creation.unknown
java.net.BindException: Could not start Webster.
at org.rioproject.tools.webster.Webster.initialize(Webster.java:254) ~[na:na]
at org.rioproject.tools.webster.Webster.<init>(Webster.java:203) ~[na:na]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.7.0_79]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) ~[na:1.7.0_79]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.7.0_79]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) ~[na:1.7.0_79]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:344) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.788 org.rioproject.start - service.creation.unknown.detail 0 RioServiceDescriptor codebase: , policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/webster-5.1.4.jar, implClassName: org.rioproject.tools.webster.Webster, serverConfigArgs: [-roots, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/deploy;/home/pubudu/.m2/repository, -bindAddress, 10.101.9.131, -port, 9010], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.789 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.789 org.rioproject.start - service.creation.unknown.detail 1 RioServiceDescriptor codebase: artifact:org.apache.river/reggie-dl/2.2.2;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/reggie-2.2.2.jar, implClassName: com.sun.jini.reggie.TransientRegistrarImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/reggie.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown.detail 2 RioServiceDescriptor codebase: artifact:org.rioproject.monitor/monitor-proxy/5.1.4;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/monitor-service-5.1.4.jar, implClassName: org.rioproject.monitor.service.ProvisionMonitorImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/monitor.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.791 org.rioproject.start - service.creation.unknown.detail 3 RioServiceDescriptor codebase: artifact:org.rioproject.cybernode/cybernode-proxy/5.1.4;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/cybernode-service-5.1.4.jar, implClassName: org.rioproject.cybernode.service.CybernodeImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/cybernode.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/compute_resource.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
Can someone point me towards the correct direction to get the examples running?
I am trying out the calculator example.
Using RIO version 5.1.4
JDK version j1.7.0_79
Maven version 3.3.3
on Ubuntu 14.04
When running the mvn rio:start-all command from the calculator directory it gives a build success message as follows.
rio-5.1.4/examples/calculator$ mvn rio:start-all
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Example :: Calculator
[INFO] Example :: Calculator API
[INFO] Example :: Calculator Service Implementation
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator API 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator-api ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator Service Implementation 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:start-all (default-cli) @ calculator-service ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Example :: Calculator .............................. SUCCESS [ 0.295 s]
[INFO] Example :: Calculator API .......................... SUCCESS [ 0.002 s]
[INFO] Example :: Calculator Service Implementation ....... SUCCESS [ 0.001 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.893 s
[INFO] Finished at: 2015-05-06T15:05:25+05:30
[INFO] Final Memory: 11M/239M
[INFO] ------------------------------------------------------------------------
is this the expected output or should some applications start up as a result of this command?
Next when I run the mvn rio:deploy command from the command line the following is the output.
rio/rio-5.1.4/examples/calculator$ mvn rio:deploy
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Example :: Calculator
[INFO] Example :: Calculator API
[INFO] Example :: Calculator Service Implementation
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator ---
total 0
discovery time 5005 millis, timeout used 5000
No Provision Monitor instances discovered
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator API 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator-api ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example :: Calculator Service Implementation 2.3.3
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @ calculator-service ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Example :: Calculator .............................. SUCCESS [ 7.931 s]
[INFO] Example :: Calculator API .......................... SUCCESS [ 0.002 s]
[INFO] Example :: Calculator Service Implementation ....... SUCCESS [ 0.001 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.504 s
[INFO] Finished at: 2015-05-06T15:06:52+05:30
[INFO] Final Memory: 8M/239M
[INFO] ------------------------------------------------------------------------
mvn rio:ui gives the ui with "waiting to discovery the Rio system".
When I run rio from the command line following is the output
./bin/rio start all
INFO 15:08:57 starter config [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/start-all.groovy]
INFO 15:08:59.447 org.rioproject.config.RioProperties - /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/rio.env not found, skipping
WARN 15:08:59.788 org.rioproject.start - service.creation.unknown
java.net.BindException: Could not start Webster.
at org.rioproject.tools.webster.Webster.initialize(Webster.java:254) ~[na:na]
at org.rioproject.tools.webster.Webster.<init>(Webster.java:203) ~[na:na]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.7.0_79]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) ~[na:1.7.0_79]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.7.0_79]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) ~[na:1.7.0_79]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:344) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.788 org.rioproject.start - service.creation.unknown.detail 0 RioServiceDescriptor codebase: , policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/webster-5.1.4.jar, implClassName: org.rioproject.tools.webster.Webster, serverConfigArgs: [-roots, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/deploy;/home/pubudu/.m2/repository, -bindAddress, 10.101.9.131, -port, 9010], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.789 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.789 org.rioproject.start - service.creation.unknown.detail 1 RioServiceDescriptor codebase: artifact:org.apache.river/reggie-dl/2.2.2;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/reggie-2.2.2.jar, implClassName: com.sun.jini.reggie.TransientRegistrarImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/reggie.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown.detail 2 RioServiceDescriptor codebase: artifact:org.rioproject.monitor/monitor-proxy/5.1.4;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/monitor-service-5.1.4.jar, implClassName: org.rioproject.monitor.service.ProvisionMonitorImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/monitor.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
WARN 15:08:59.790 org.rioproject.start - service.creation.unknown
java.net.MalformedURLException: unknown protocol: artifact
at java.net.URL.<init>(URL.java:592) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:482) ~[na:1.7.0_79]
at java.net.URL.<init>(URL.java:431) ~[na:1.7.0_79]
at com.sun.jini.start.ClassLoaderUtil.getCodebaseURLs(ClassLoaderUtil.java:103) ~[start-2.2.2.jar:na]
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:303) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:229) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:346) ~[rio-start-5.1.4.jar:5.1.4]
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:440) ~[rio-start-5.1.4.jar:5.1.4]
WARN 15:08:59.791 org.rioproject.start - service.creation.unknown.detail 3 RioServiceDescriptor codebase: artifact:org.rioproject.cybernode/cybernode-proxy/5.1.4;http://10.101.9.131:9010, policy: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/policy/policy.all, classpath: /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/lib/cybernode-service-5.1.4.jar, implClassName: org.rioproject.cybernode.service.CybernodeImpl, serverConfigArgs: [/home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/common.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/cybernode.groovy, /home/pubudu/projects/catnet/learn/rio/rio-5.1.4/config/compute_resource.groovy], lifeCycle: org.rioproject.start.RioServiceDescriptor$1@4a6cef0f
Can someone point me towards the correct direction to get the examples running?
Dennis Reedy
May 6, 2015, 10:51:06 AM5/6/15
to rio-...@googlegroups.com
As referenced earlier in the group there is a defect that was released in 5.1.4, apologies for that. I’ve just pushed 5.1.5 that addresses that defect. Please download 5.1.5 and follow the steps you’ve outlined below.
Regards
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+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Zsolt Kúti
May 18, 2015, 4:53:02 AM5/18/15
to rio-...@googlegroups.com
Hi Dennis,
Although I run into this issue too, I had no time to report.
Thanks for this update.
Now, the workflow example still errs [1].
It seems as if other version of Entry (Javaspaces?) was found. There
are others instances present on the network (under different groups), so
it could be rightfully so. What configuration the example needs to avoid
finding them?
Removing net cable results in name resolving problem [2].
Attempts to set java.rmi.server.hostname or
java.rmi.server.useLocalHostname did not help. What I do not get
why the error refers to Inet6AddressImpl as no network interface is
configured for ipv6.
Thanks.
Zsolt
[1]
máj. 18, 2015 10:19:11 DE com.sun.jini.reggie.RegistrarProxy
handleException INFO: unmarshalling failure
java.rmi.UnmarshalException: incoming entry type: class
com.sun.jini.reggie.EntryClass[name=org.rioproject.entry.StandardServiceType,
hash=-8676480473068892386] is not assignable to the local version of
the type: class
com.sun.jini.reggie.EntryClass[name=org.rioproject.entry.StandardServiceType,
hash=6542888045916027194] at
com.sun.jini.reggie.EntryClass.toClass(EntryClass.java:186) at
com.sun.jini.reggie.EntryRep.get(EntryRep.java:98) at
com.sun.jini.reggie.EntryRep.toEntry(EntryRep.java:202) at
com.sun.jini.reggie.Item.get(Item.java:145) at
com.sun.jini.reggie.Item.toServiceItem(Item.java:177) at
com.sun.jini.reggie.Matches.get(Matches.java:62) at
com.sun.jini.reggie.RegistrarProxy.lookup(RegistrarProxy.java:128) at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupTask.run(ServiceDiscoveryManager.java:955)
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$RegisterListenerTask.run(ServiceDiscoveryManager.java:925)
at com.sun.jini.thread.TaskManager$TaskThread.run(TaskManager.java:331)
total 1
discovery time 651 millis, timeout used 5000
java.rmi.UnmarshalException: error unmarshalling response; nested
exception is: java.lang.ClassNotFoundException: error creating dynamic
proxy class at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethodOnce(BasicInvocationHandler.java:854)
at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethod(BasicInvocationHandler.java:659)
at
net.jini.jeri.BasicInvocationHandler.invoke(BasicInvocationHandler.java:528)
at com.sun.proxy.$Proxy12.getAdmin(Unknown Source) at
org.rioproject.resources.servicecore.AbstractProxy.getAdmin(AbstractProxy.java:164)
at
org.rioproject.tools.cli.ServiceFinder.getPreparedAdmin(ServiceFinder.java:817)
at
org.rioproject.tools.cli.MonitorControl$DeployHandler.deploy(MonitorControl.java:203)
at
org.rioproject.tools.cli.MonitorControl$DeployHandler.process(MonitorControl.java:148)
at org.rioproject.tools.cli.CLI.doInit(CLI.java:1534) at
org.rioproject.tools.cli.CLI.initCLI(CLI.java:1434) at
org.rioproject.tools.cli.CLI.main(CLI.java:1584) Caused by:
java.lang.ClassNotFoundException: error creating dynamic proxy class at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:700) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:669) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:610) at
java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:646)
at
org.rioproject.rmi.ResolvingLoader.loadProxyClass(ResolvingLoader.java:91)
at
java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:311)
at net.jini.loader.ClassLoading.loadProxyClass(ClassLoading.java:240)
at
net.jini.io.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:373)
at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1558)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1514)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
at
java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:500)
at
org.rioproject.resources.servicecore.ServiceAdminProxy.readObject(ServiceAdminProxy.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606) at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at
com.sun.jini.jeri.internal.runtime.Util.unmarshalValue(Util.java:221)
at
net.jini.jeri.BasicInvocationHandler.unmarshalReturn(BasicInvocationHandler.java:1242)
at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethodOnce(BasicInvocationHandler.java:825) ...
10 more Caused by: java.lang.IllegalArgumentException: methods with
same signature getServiceElement() but incompatible return types:
[class org.rioproject.core.ServiceElement, class
org.rioproject.opstring.ServiceElement] at
sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) at
sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) at
sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) at
java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:672) at
java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:592) at
java.lang.reflect.WeakCache$Factory.get(WeakCache.java:244) at
java.lang.reflect.WeakCache.get(WeakCache.java:141) at
java.lang.reflect.Proxy.getProxyClass0(Proxy.java:455) at
java.lang.reflect.Proxy.getProxyClass(Proxy.java:405) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:698) ...
36 more Problem deploying [Workflow Example], Exception : error
unmarshalling response; nested exception is:
java.lang.ClassNotFoundException: error creating dynamic proxy class
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] Building Example :: Workflow API 2.3.4 [INFO]
------------------------------------------------------------------------
[INFO] Building Example :: Workflow Service Implementation 2.3.4 [INFO]
Example :: Workflow API ........................... SUCCESS [0.001s]
[INFO] Example :: Workflow Service Implementation ........ SUCCESS
[0.002s] [INFO]
2015 [INFO] Final Memory: 8M/140M [INFO]
------------------------------------------------------------------------
[2]
Exception initializing system [java.net.UnknownHostException:
kuti-zsolt: hostname nor servname provided, or not known], check log
for details java.net.UnknownHostException: kuti-zsolt: hostname nor
servname provided, or not known at
java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at
java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293)
at java.net.InetAddress.getLocalHost(InetAddress.java:1469) at
net.jini.discovery.LookupDiscovery.getLocalHost(LookupDiscovery.java:2396)
at net.jini.discovery.LookupDiscovery.init(LookupDiscovery.java:3174)
at
net.jini.discovery.LookupDiscovery.beginDiscovery(LookupDiscovery.java:3086)
at net.jini.discovery.LookupDiscovery.<init>(LookupDiscovery.java:1946)
at
net.jini.discovery.LookupDiscoveryManager.beginDiscovery(LookupDiscoveryManager.java:1549)
at
net.jini.discovery.LookupDiscoveryManager.<init>(LookupDiscoveryManager.java:966)
at
org.rioproject.impl.client.DiscoveryManagementPool$SharedDiscoveryManager.<init>(DiscoveryManagementPool.java:531)
at
org.rioproject.impl.client.DiscoveryManagementPool$DiscoveryControl.createSharedDiscoveryManager(DiscoveryManagementPool.java:424)
at
org.rioproject.impl.client.DiscoveryManagementPool$DiscoveryControl.createLookupDiscoveryManager(DiscoveryManagementPool.java:342)
at
org.rioproject.impl.client.DiscoveryManagementPool.getDiscoveryManager(DiscoveryManagementPool.java:214)
at org.rioproject.tools.cli.ServiceFinder.<init>(ServiceFinder.java:98)
at org.rioproject.tools.cli.CLI.doInit(CLI.java:1518) at
org.rioproject.tools.cli.CLI.initCLI(CLI.java:1434) at
org.rioproject.tools.cli.CLI.main(CLI.java:1584)
On Wed, 6 May 2015 10:51:02 -0400
Dennis Reedy <dennis...@gmail.com> wrote:
> As referenced earlier in the group there is a defect that was
> released in 5.1.4, apologies for that. I’ve just pushed 5.1.5 that
> addresses that defect. Please download 5.1.5 and follow the steps
> you’ve outlined below.
...
Although I run into this issue too, I had no time to report.
Thanks for this update.
Now, the workflow example still errs [1].
It seems as if other version of Entry (Javaspaces?) was found. There
are others instances present on the network (under different groups), so
it could be rightfully so. What configuration the example needs to avoid
finding them?
Removing net cable results in name resolving problem [2].
Attempts to set java.rmi.server.hostname or
java.rmi.server.useLocalHostname did not help. What I do not get
why the error refers to Inet6AddressImpl as no network interface is
configured for ipv6.
Thanks.
Zsolt
[1]
máj. 18, 2015 10:19:11 DE com.sun.jini.reggie.RegistrarProxy
handleException INFO: unmarshalling failure
java.rmi.UnmarshalException: incoming entry type: class
com.sun.jini.reggie.EntryClass[name=org.rioproject.entry.StandardServiceType,
hash=-8676480473068892386] is not assignable to the local version of
the type: class
com.sun.jini.reggie.EntryClass[name=org.rioproject.entry.StandardServiceType,
hash=6542888045916027194] at
com.sun.jini.reggie.EntryClass.toClass(EntryClass.java:186) at
com.sun.jini.reggie.EntryRep.get(EntryRep.java:98) at
com.sun.jini.reggie.EntryRep.toEntry(EntryRep.java:202) at
com.sun.jini.reggie.Item.get(Item.java:145) at
com.sun.jini.reggie.Item.toServiceItem(Item.java:177) at
com.sun.jini.reggie.Matches.get(Matches.java:62) at
com.sun.jini.reggie.RegistrarProxy.lookup(RegistrarProxy.java:128) at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupTask.run(ServiceDiscoveryManager.java:955)
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$RegisterListenerTask.run(ServiceDiscoveryManager.java:925)
at com.sun.jini.thread.TaskManager$TaskThread.run(TaskManager.java:331)
total 1
discovery time 651 millis, timeout used 5000
java.rmi.UnmarshalException: error unmarshalling response; nested
exception is: java.lang.ClassNotFoundException: error creating dynamic
proxy class at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethodOnce(BasicInvocationHandler.java:854)
at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethod(BasicInvocationHandler.java:659)
at
net.jini.jeri.BasicInvocationHandler.invoke(BasicInvocationHandler.java:528)
at com.sun.proxy.$Proxy12.getAdmin(Unknown Source) at
org.rioproject.resources.servicecore.AbstractProxy.getAdmin(AbstractProxy.java:164)
at
org.rioproject.tools.cli.ServiceFinder.getPreparedAdmin(ServiceFinder.java:817)
at
org.rioproject.tools.cli.MonitorControl$DeployHandler.deploy(MonitorControl.java:203)
at
org.rioproject.tools.cli.MonitorControl$DeployHandler.process(MonitorControl.java:148)
at org.rioproject.tools.cli.CLI.doInit(CLI.java:1534) at
org.rioproject.tools.cli.CLI.initCLI(CLI.java:1434) at
org.rioproject.tools.cli.CLI.main(CLI.java:1584) Caused by:
java.lang.ClassNotFoundException: error creating dynamic proxy class at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:700) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:669) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:610) at
java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:646)
at
org.rioproject.rmi.ResolvingLoader.loadProxyClass(ResolvingLoader.java:91)
at
java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:311)
at net.jini.loader.ClassLoading.loadProxyClass(ClassLoading.java:240)
at
net.jini.io.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:373)
at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1558)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1514)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
at
java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:500)
at
org.rioproject.resources.servicecore.ServiceAdminProxy.readObject(ServiceAdminProxy.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606) at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at
com.sun.jini.jeri.internal.runtime.Util.unmarshalValue(Util.java:221)
at
net.jini.jeri.BasicInvocationHandler.unmarshalReturn(BasicInvocationHandler.java:1242)
at
net.jini.jeri.BasicInvocationHandler.invokeRemoteMethodOnce(BasicInvocationHandler.java:825) ...
10 more Caused by: java.lang.IllegalArgumentException: methods with
same signature getServiceElement() but incompatible return types:
[class org.rioproject.core.ServiceElement, class
org.rioproject.opstring.ServiceElement] at
sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) at
sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) at
sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) at
java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:672) at
java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:592) at
java.lang.reflect.WeakCache$Factory.get(WeakCache.java:244) at
java.lang.reflect.WeakCache.get(WeakCache.java:141) at
java.lang.reflect.Proxy.getProxyClass0(Proxy.java:455) at
java.lang.reflect.Proxy.getProxyClass(Proxy.java:405) at
sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:698) ...
36 more Problem deploying [Workflow Example], Exception : error
unmarshalling response; nested exception is:
java.lang.ClassNotFoundException: error creating dynamic proxy class
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] Building Example :: Workflow API 2.3.4 [INFO]
------------------------------------------------------------------------
[INFO] [INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @
workflow-api --- [INFO] [INFO]
[INFO] [INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @
------------------------------------------------------------------------
[INFO] Building Example :: Workflow Service Implementation 2.3.4 [INFO]
------------------------------------------------------------------------
[INFO] [INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @
workflow-service --- [INFO]
[INFO] [INFO] --- maven-rio-plugin:5.1:deploy (default-cli) @
------------------------------------------------------------------------
[INFO] Reactor Summary: [INFO] [INFO] Example ::
Workflow ............................... SUCCESS [3.359s] [INFO]
[INFO] Reactor Summary: [INFO] [INFO] Example ::
Example :: Workflow API ........................... SUCCESS [0.001s]
[INFO] Example :: Workflow Service Implementation ........ SUCCESS
[0.002s] [INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS [INFO]
------------------------------------------------------------------------
[INFO] Total time: 3.822s [INFO] Finished at: Mon May 18 10:19:12 CEST
[INFO] BUILD SUCCESS [INFO]
------------------------------------------------------------------------
2015 [INFO] Final Memory: 8M/140M [INFO]
------------------------------------------------------------------------
[2]
Exception initializing system [java.net.UnknownHostException:
kuti-zsolt: hostname nor servname provided, or not known], check log
for details java.net.UnknownHostException: kuti-zsolt: hostname nor
servname provided, or not known at
java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at
java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293)
at java.net.InetAddress.getLocalHost(InetAddress.java:1469) at
net.jini.discovery.LookupDiscovery.getLocalHost(LookupDiscovery.java:2396)
at net.jini.discovery.LookupDiscovery.init(LookupDiscovery.java:3174)
at
net.jini.discovery.LookupDiscovery.beginDiscovery(LookupDiscovery.java:3086)
at net.jini.discovery.LookupDiscovery.<init>(LookupDiscovery.java:1946)
at
net.jini.discovery.LookupDiscoveryManager.beginDiscovery(LookupDiscoveryManager.java:1549)
at
net.jini.discovery.LookupDiscoveryManager.<init>(LookupDiscoveryManager.java:966)
at
org.rioproject.impl.client.DiscoveryManagementPool$SharedDiscoveryManager.<init>(DiscoveryManagementPool.java:531)
at
org.rioproject.impl.client.DiscoveryManagementPool$DiscoveryControl.createSharedDiscoveryManager(DiscoveryManagementPool.java:424)
at
org.rioproject.impl.client.DiscoveryManagementPool$DiscoveryControl.createLookupDiscoveryManager(DiscoveryManagementPool.java:342)
at
org.rioproject.impl.client.DiscoveryManagementPool.getDiscoveryManager(DiscoveryManagementPool.java:214)
at org.rioproject.tools.cli.ServiceFinder.<init>(ServiceFinder.java:98)
at org.rioproject.tools.cli.CLI.doInit(CLI.java:1518) at
org.rioproject.tools.cli.CLI.initCLI(CLI.java:1434) at
org.rioproject.tools.cli.CLI.main(CLI.java:1584)
On Wed, 6 May 2015 10:51:02 -0400
Dennis Reedy <dennis...@gmail.com> wrote:
> As referenced earlier in the group there is a defect that was
> released in 5.1.4, apologies for that. I’ve just pushed 5.1.5 that
> addresses that defect. Please download 5.1.5 and follow the steps
> you’ve outlined below.
Reply all
Reply to author
Forward
0 new messages