THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This article has the following structure:
Geronimo configuration
...
Configure the server to use Harmony RMI Registry provider for JNDI
Harmony places JNDI providers in org.apache.harmony.jndi package tree, not in com.sun.jndi like Sun Java does, so you have to point Geronimo into the right direction to locate and properly access the RMI Registry provider.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<module name="org.apache.geronimo.configs/j2ee-corba-yoko/2.0.2/car">
<gbean name="CORBASSLConfig">
<attribute name="protocol">TLS</attribute>
</gbean>
</module>
|
Change default keystore type
Geronimo uses JKS keystore that Harmony doesn't support. For now, there's no way to workaround this problem except by patching the Geronimo source code. See GERONIMO-2015 for details.
Customize the server startup
...
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.
Other issues
GERONIMO-2014 - Geronimo uses outdated version of ApacheDS
GERONIMO-2015 - Let's replace JKS to PKCS12 key store type
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
MX4J/commons-logging problem
GERONIMO-2595 - Hardcoded MX4J logger in org.apache.geronimo.kernel.log.GeronimoLogging class
HARMONY-1259 - NoClassDefFoundError while working with MX4J loggers
Looks like this issue is not longer actual.
Test problems
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-2055 - RunningTest is not compatible with non-Sun VMs