Issue Details (XML | Word | Printable)

Key: RIO-228
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dennis Reedy
Reporter: Dennis Reedy
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Rio

Unable to debug service when loading with opstring

Created: 16/Mar/10 02:18 PM   Updated: 16/Mar/10 03:40 PM
Component/s: Test
Affects Version/s: 4.0 M3
Fix Version/s: 4.0

Time Tracking:
Not Specified


 Description  « Hide
When starting the StaticCybernode with an opstring argument that uses resources to declare jars and does not have a codebase declared we get the following exception:

java.net.MalformedURLException: no protocol:
nullPSMC/lib/PSMC-meter-0.1.jar at java.net.URL.<init>(URL.java:567) at
java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413)
at org.rioproject.core.ClassBundle.urlsFromJARs(ClassBundle.java:482)
at org.rioproject.core.ClassBundle.getJARs(ClassBundle.java:324) at
org.rioproject.cybernode.ServiceBeanLoader.provisionService(ServiceBeanLoader.java:993) at
org.rioproject.cybernode.ServiceBeanLoader.load(ServiceBeanLoader.java:246)
at org.rioproject.cybernode.JSBDelegate$1.run(JSBDelegate.java:519)
org.rioproject.core.JSBInstantiationException:
java.net.MalformedURLException: no protocol:
nullPSMC/lib/PSMC-meter-0.1.jar at java.net.URL.<init>(URL.java:567) at
java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413)
at org.rioproject.core.ClassBundle.urlsFromJARs(ClassBundle.java:482)
at org.rioproject.core.ClassBundle.getJARs(ClassBundle.java:324) at
org.rioproject.cybernode.ServiceBeanLoader.provisionService(ServiceBeanLoader.java:993) at
org.rioproject.cybernode.ServiceBeanLoader.load(ServiceBeanLoader.java:246)
at org.rioproject.cybernode.JSBDelegate$1.run(JSBDelegate.java:519)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dennis Reedy added a comment - 16/Mar/10 03:40 PM
Check if we are running the StaticCybernode. If so, do not get the jars from the respective ClassBundles since they are expected to be on the classpath.