rio workflow example - resolve problem

[Zsolt Kúti]

Hi Dennis,

Due to the unsuccessful trials with the test webapp I try to run the
examples. Calculator works fine (just to be sure the simplest is
working), but moving on to workflow brought up something.
Aether can't resolve needed dependency (outrigger-dl).

During installation of examples maven resolved a ton of
dependencies, so that part is OK.

resolverConfig.groovy in Rio is untouched.

outrigger-dl in local .m2 is missing, only an an empty dir what I see.
What is needed for Aether to be able to resolve runtime dependencies?

Thanks!
Zsolt



Caused by: org.rioproject.resolver.ResolverException: While trying to
resolve org.apache.river:outrigger-dl:2.2.2 at
org.rioproject.resolver.aether.AetherResolver.getClassPathFor(AetherResolver.java:126)
at
org.rioproject.monitor.service.DeploymentVerifier.resolve(DeploymentVerifier.java:134)
at
org.rioproject.monitor.service.DeploymentVerifier.resolveOperationalStringService(DeploymentVerifier.java:107)
at
org.rioproject.monitor.service.DeploymentVerifier.verifyOperationalStringService(DeploymentVerifier.java:90)
at
org.rioproject.monitor.service.DeploymentVerifier.verifyOperationalString(DeploymentVerifier.java:76)
at
org.rioproject.monitor.service.DeploymentVerifier.verifyDeploymentRequest(DeploymentVerifier.java:68)
at
org.rioproject.monitor.service.ProvisionMonitorImpl.deploy(ProvisionMonitorImpl.java:527)
at
org.rioproject.monitor.service.ProvisionMonitorAdminImpl.deploy(ProvisionMonitorAdminImpl.java:137)
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
net.jini.jeri.BasicInvocationDispatcher.invoke(BasicInvocationDispatcher.java:1126)
at
net.jini.jeri.BasicInvocationDispatcher.dispatch(BasicInvocationDispatcher.java:608)
at com.sun.jini.jeri.internal.runtime.Target$2.run(Target.java:487) at
net.jini.export.ServerContext.doWithServerContext(ServerContext.java:108)
at com.sun.jini.jeri.internal.runtime.Target.dispatch(Target.java:484)
at com.sun.jini.jeri.internal.runtime.Target.access$000(Target.java:57)
at com.sun.jini.jeri.internal.runtime.Target$1.run(Target.java:464) at
com.sun.jini.start.AggregatePolicyProvider$AggregateSecurityContext$2.run(AggregatePolicyProvider.java:527)
at java.security.AccessController.doPrivileged(Native Method) at
com.sun.jini.jeri.internal.runtime.Target.dispatch(Target.java:461) at
com.sun.jini.jeri.internal.runtime.Target.dispatch(Target.java:426) at
com.sun.jini.jeri.internal.runtime.DgcRequestDispatcher.dispatch(DgcRequestDispatcher.java:210)
at
net.jini.jeri.connection.ServerConnectionManager$Dispatcher.dispatch(ServerConnectionManager.java:147)
at com.sun.jini.jeri.internal.mux.MuxServer$1$1.run(MuxServer.java:244)
at
com.sun.jini.start.AggregatePolicyProvider$AggregateSecurityContext$1.run(AggregatePolicyProvider.java:513)
at java.security.AccessController.doPrivileged(Native Method) at
com.sun.jini.jeri.internal.mux.MuxServer$1.run(MuxServer.java:241) at
com.sun.jini.thread.ThreadPool$Worker.run(ThreadPool.java:136) at
java.lang.Thread.run(Thread.java:745) Caused by:
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) at
java.util.concurrent.FutureTask.get(FutureTask.java:188) at
org.rioproject.resolver.aether.AetherResolver.getClassPathFor(AetherResolver.java:122) ...
30 more Caused by: java.lang.NullPointerException at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:361)
at
org.rioproject.resolver.aether.AetherService.resolve(AetherService.java:264)
at
org.rioproject.resolver.aether.AetherResolver$ResolvingRequestTask.call(AetherResolver.java:319)
at
org.rioproject.resolver.aether.AetherResolver$ResolvingRequestTask.call(AetherResolver.java:302)
at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

[Dennis Reedy]

Hi Zsolt,

If you cannot resolve the outrigger-dl artifact, this has to be related to your proxy configuration issue you raised earlier.

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]

On Mon, 4 May 2015 09:10:56 -0400
Dennis Reedy <dennis...@gmail.com> wrote:


> Hi Zsolt,

> If you cannot resolve the outrigger-dl artifact, this has to be
> related to your proxy configuration issue you raised earlier.

Do your refer to maven proxy settings?

Now, setting is there and I can see its working when I "mvn install" the
Rio examples. But then the workflow example fails to deploy.
I explain it to myself, perhaps wrongly, as:
- maven has its own resolver, which needs settings.xml, during install
phase no *-dl is required
- Rio uses Aether which requires a different way for proxy settings,
and when *-dl dependency is found could not be accessed due to this
missing proxy setting

I have seen some reference for proxy settings for Aether
(like https://jira.grails.org/browse/GRAILS-10097), but had no time to
delve into it.

Zsolt