Bugzilla – Full Text Bug Listing
| Summary: | NoClassDefFoundError when starting server from tooling | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Glyn Normington <glyn.normington> |
| Component: | unknown | Assignee: | Glyn Normington <glyn.normington> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 2.1.0.M05-incubation | ||
| Target Milestone: | 2.1.0.M06-incubation | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
This will be fixed in 2.1.0.M06-incubation. Meanwhile the tooling can be reconfigured to work around the problem as follows: 1. Open the Servers window in the tooling. 2. Determine the Virgo server to be reconfigured. 3. Double click the Virgo server to open up the server window. 4. Navigate to the "Overview" pane. 5. Click the "Open launch configuration" link. 6. Navigate to the "Classpath" pane. 7. Select "User Entries". 8. Add each of the 5 JARs in the launcher directory to the classpath in turn (the order does not matter), by clicking "Add External JARs...", navigating to $SERVER_HOME/lib/launcher, and adding the JARs as necessary. 9. Back on the "Classpath" pane, once all 5 JARs have been added, click "Apply" then "Ok". It should now be possible to launch Virgo as usual. Milestone 6 works ok with the tooling - problem fixed. |
When an attempt is made to start Virgo 2.1.0.M05-incubation using the Eclipse tooling, the following exception occurs: xception in thread "main" java.lang.NoClassDefFoundError: org/eclipse/virgo/osgi/launcher/Launcher Caused by: java.lang.ClassNotFoundException: org.eclipse.virgo.osgi.launcher.Launcher at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248)