• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 MikePotter(DFS) commented Permalink

How would setting translate into a RAD 8.0 run configuration for a Java test program project? I get class not found from the loader debugging as RAD run configurations do not put each app jar in the RAD project on the class path. Meanwhile I will try adding the jar file on the Build Path dialog/Order Export tab see if that explicitly adds the jar file to the run configuration classpath.

In the RAD run configuration VM args I put -Dibm.cl.verbose=*MyClass MyClass . The loader debugging is invoked. However the loader debugging is not able to find the class located in a jar file at the RAD project root. The reason already noted is the RAD run config does not set the classpath for each jar file and the loader debugging seems to ignores the RAD classpath of the project where the jar files are located as a wildcard to search. Here is the error (edited for confidentiality, replaced with MyClass):
AppClassLoader could not find MyClass
Exception in thread "main" java.lang.NoClassDefFoundError: MyClass
Caused by: java.lang.ClassNotFoundException: MyClass
at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:660)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:626)

2 MikePotter(DFS) commented Permalink

Update from earlier comment. The jar file containing the class to trace is on the classpath defined by the JVM property java.class.path . However the loader debugging is not using that classpath.

I added the jar file with the class in question to the RAD 8 run config dialog Order Export tab. In the RAD test project class main() have this code to display the java.class.path:
System.out.println("java.class.path=" + System.getProperty("java.class.path") + "\n");

Add a Comment Add a Comment