Re: [rvm-research] Jikes missing seemingly random standard java classes

I suspect that what is happening is that there's an error running a 
class initializer, that's being interpreted as the class not being 
found.  The CNFE could be what's known around these parts as a Furphy.

Rounding up the usual suspects, the first thing to check is presence of 
libraries.  If you do

$ ldd dist/<build>/JikesRVM and look for any libraries that aren't found.


Another approach would be to debug why it doesn't build on Debian - the 
usual suspect is missing packages: cross-building might get around that 
at build time just to bite you at runtime. So what happens when you try 
to build on Debian ?

cheers,
Robin

On 13/10/14 09:49, Jacob Strohm wrote:
> Hi all,
>
>     My name is Jacob, I'm a student at SUNY Binghamton doing research on
> an energy-aware JVM.
>
>     I am attempting to build and run jikesrvm (from the latest tarball
> on Sourceforge) on an x86_64 Debian Squeeze machine.  So far I have
> gotten the build to "succeed" in two ways:
>      -a local build, built on the machine itself with ant, and
>      -a remote build, built with bin/buildit on my Ubuntu 14.04 laptop
> with the Debian machine specified with the -c option of the script.
>
> In both cases the executable is successfully generated, and it runs fine
> on Ubuntu.  On Debian, however, both executables give the same error
> when run (full output at bottom):
>      WARNING: error instantiating 'java.util.logging.ConsoleHandler'
> referenced by handlers, class not found
>      java.lang.ClassNotFoundException: java.util.logging.ConsoleHandler
> followed by a stack trace, then
>      Exception in thread "Jikes_RBoot_Thread":
> java.lang.NoClassDefFoundError: Could not find the class
> java.beans.PropertyChangeEvent:
>
> I wasn't able to find anything related on Google.  I can see
> that components/classpath/97.2p13/classpath/java/util/logging/ConsoleHandler.java
> is present, as well
> as components/classpath/97.2p13/classpath/java/beans/PropertyChangeEvent.java.
> The stack trace lists other standard java classes, so I don't understand
> why these ones are apparently absent.  What might cause jikesrvm to be
> missing these classes?
>
> Full output for reference:
> WARNING: error instantiating 'java.util.logging.ConsoleHandler'
> referenced by handlers, class not found
> java.lang.ClassNotFoundException: java.util.logging.ConsoleHandler
>     at java.lang.Exception.<init>(Exception.java:78)
>     at
> java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:84)
>     at
> org.jikesrvm.classloader.BootstrapClassLoader.findClass(BootstrapClassLoader.java:191)
>     at
> org.jikesrvm.classloader.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:148)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:293)
>     at
> org.jikesrvm.classloader.TypeReference.resolveInternal(TypeReference.java:811)
>     at
> org.jikesrvm.classloader.TypeReference.resolve(TypeReference.java:799)
>     at java.lang.Class.forNameInternal(Class.java:819)
>     at java.lang.Class.forName(Class.java:806)
>     at java.util.logging.LogManager.locateClass(LogManager.java:923)
>     at java.util.logging.LogManager.createInstance(LogManager.java:852)
>     at java.util.logging.LogManager.readConfiguration(LogManager.java:572)
>     at java.util.logging.LogManager.readConfiguration(LogManager.java:527)
>     at java.util.logging.LogManager.initLogManager(LogManager.java:203)
>     at java.util.logging.LogManager.getLogManager(LogManager.java:168)
>     at java.util.logging.Logger.getLogger(Logger.java:252)
>     at java.util.logging.Logger.getLogger(Logger.java:211)
>     at java.util.logging.Logger$1.run(Logger.java:94)
>     at java.security.AccessController.doPrivileged(AccessController.java:96)
>     at java.util.logging.Logger.<clinit>(Logger.java:90)
>     at org.jikesrvm.VM.runClassInitializer(VM.java:554)
>     at org.jikesrvm.VM.finishBooting(VM.java:415)
>     at org.jikesrvm.VM.boot(VM.java:147)
> Exception in thread "Jikes_RBoot_Thread":
> java.lang.NoClassDefFoundError: Could not find the class
> java.beans.PropertyChangeEvent:
> java.beans.PropertyChangeEvent
>     at java.lang.Error.<init>(Error.java:81)
>     at java.lang.LinkageError.<init>(LinkageError.java:72)
>     at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:74)
>     at
> org.jikesrvm.classloader.TypeReference.resolveInternal(TypeReference.java:813)
>     at
> org.jikesrvm.classloader.TypeReference.resolve(TypeReference.java:799)
>     at
> org.jikesrvm.runtime.RuntimeEntrypoints.unresolvedNewScalar(RuntimeEntrypoints.java:264)
>     at
> java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:332)
>     at java.util.logging.LogManager.readConfiguration(LogManager.java:613)
>     at java.util.logging.LogManager.readConfiguration(LogManager.java:527)
>     at java.util.logging.LogManager.initLogManager(LogManager.java:203)
>     at java.util.logging.LogManager.getLogManager(LogManager.java:168)
>     at java.util.logging.Logger.getLogger(Logger.java:252)
>     at java.util.logging.Logger.getLogger(Logger.java:211)
>     at java.util.logging.Logger$1.run(Logger.java:94)
>     at java.security.AccessController.doPrivileged(AccessController.java:96)
>     at java.util.logging.Logger.<clinit>(Logger.java:90)
>     at org.jikesrvm.VM.runClassInitializer(VM.java:554)
>     at org.jikesrvm.VM.finishBooting(VM.java:415)
>     at org.jikesrvm.VM.boot(VM.java:147)
> Caused by: java.lang.ClassNotFoundException: java.beans.PropertyChangeEvent
>     at java.lang.Exception.<init>(Exception.java:78)
>     at
> java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:84)
>     at
> org.jikesrvm.classloader.BootstrapClassLoader.findClass(BootstrapClassLoader.java:191)
>     at
> org.jikesrvm.classloader.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:148)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:293)
>     at
> org.jikesrvm.classloader.TypeReference.resolveInternal(TypeReference.java:811)
>     ...15 more
>
> Thanks,
> Jacob
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
>
>
>
> _______________________________________________
> Jikesrvm-researchers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
>


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho