You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

 Sample applications Creating a new sample

Running Geronimo on Harmony

This article describes the ways and known issues to run Geronimo v2.0.1 using Apache Harmony as a JVM.

ToDo

This article has the following structure:

General notes

Using DRLVM

You should use DRLVM (Harmony VM) to run Geronimo.

Harmony also supports IBM J9 VM, but Geronimo doesn't work with it, as Geronimo relies on java.util.concurrent package that requires a proper implementation of sun.misc.Unsafe class that is missing in IBM J9 VM.

Adjustments required in Geronimo

ToDo

ToDo

Adjustments required in Harmony

ToDo

ToDo

Other issues

GERONIMO-1804 - The name of JNDI/RMI service provider is hardcoded in the sources
GERONIMO-1805 - org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs
GERONIMO-1826 - Naming tests might not work on non-Sun VMs
GERONIMO-1832 - Non-public Sun classes dependencies in tests
GERONIMO-1833 - Non-public Sun classes dependencies in tests
GERONIMO-1840 - NamingPropertiesTest is not compatible with non-Sun VMs
GERONIMO-1841 - JMS connector fails to start if <name> is used instead of <gbean-link>
GERONIMO-2014 - Geronimo uses outdated version of ApacheDS
GERONIMO-2015 - Let's replace JKS to PKCS12 key store type
GERONIMO-2055 - RunningTest is not compatible with non-Sun VMs
GERONIMO-2113 - Geronimo doesn't start if restarted using another JDK
GERONIMO-2128 - Allow user to specify the Isolation Level for a CMP bean's SQL access
GERONIMO-2595 - Hardcoded MX4J logger in org.apache.geronimo.kernel.log.GeronimoLogging class

HARMONY-1259 - NoClassDefFoundError while working with MX4J loggers

  • No labels