org.rioproject.resolver.ResolverException: Error locating org.rioproject.monitor:monitor-proxy:5.0-M3: Could not find artifact org.rioproject.monitor:monitor-proxy:jar:5.0-M3 in central (http://repo1.maven.org/maven2/)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Gus Heck, 10 months ago
Error locating org.rioproject.monitor:monitor-proxy:5.0-M3: Could not find artifact org.rioproject.monitor:monitor-proxy:jar:5.0-M3 in central (http://repo1.maven.org/maven2/)
org.rioproject.resolver.ResolverException: Error locating org.rioproject.monitor:monitor-proxy:5.0-M3: Could not find artifact org.rioproject.monitor:monitor-proxy:jar:5.0-M3 in central (http://repo1.maven.org/maven2/)
at org.rioproject.resolver.aether.AetherResolver.getLocation(AetherResolver.java:163)
at org.rioproject.url.artifact.Handler.openConnection(Handler.java:101)
at java.net.URL.openConnection(URL.java:971)
at sun.rmi.server.LoaderHandler.getClassAnnotation(LoaderHandler.java:252)
at org.rioproject.rmi.ResolvingLoader.getClassAnnotation(ResolvingLoader.java:112)
at java.rmi.server.RMIClassLoader.getClassAnnotation(RMIClassLoader.java:381)
at sun.rmi.server.MarshalOutputStream.annotateClass(MarshalOutputStream.java:93)
at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1289)
at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1230)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1426)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
at org.rioproject.monitor.ProvisionMonitorImpl.createProxy(ProvisionMonitorImpl.java:261)
at org.rioproject.jsb.ServiceBeanAdapter.getServiceProxy(ServiceBeanAdapter.java:613)
at org.rioproject.resources.servicecore.ServiceProvider.register(ServiceProvider.java:157)
at org.rioproject.jsb.ServiceBeanAdapter.initializeJMX(ServiceBeanAdapter.java:452)
at org.rioproject.jsb.ServiceBeanAdapter.initialize(ServiceBeanAdapter.java:416)
at org.rioproject.jsb.ServiceBeanAdapter.initialize(ServiceBeanAdapter.java:339)
at org.rioproject.monitor.ProvisionMonitorImpl.initialize(ProvisionMonitorImpl.java:796)
at org.rioproject.jsb.ServiceBeanAdapter.doStart(ServiceBeanAdapter.java:319)
at org.rioproject.jsb.ServiceBeanAdapter.access$000(ServiceBeanAdapter.java:104)
at org.rioproject.jsb.ServiceBeanAdapter$1.run(ServiceBeanAdapter.java:244)
at org.rioproject.jsb.ServiceBeanAdapter.start(ServiceBeanAdapter.java:257)
at org.rioproject.monitor.ProvisionMonitorImpl.bootstrap(ProvisionMonitorImpl.java:157)
at org.rioproject.monitor.ProvisionMonitorImpl.(ProvisionMonitorImpl.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at org.rioproject.start.RioServiceDescriptor.create(RioServiceDescriptor.java:351)
at org.rioproject.start.ServiceStarter.create(ServiceStarter.java:227)
at org.rioproject.start.ServiceStarter.doStart(ServiceStarter.java:316)
at org.rioproject.start.ServiceStarter.main(ServiceStarter.java:408)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.