Page History

...

This article has the following structure:

• #General note
• #Unresolved issues
• #Geronimo configuration
  • #Configure the server to use Harmony RMI Registry provider for JNDI
  • #Use TLS instead of SSL
  • #Change default keystore type
  • #Customize the server startup
  • #Use HTTPS web interface
  • #Configure Deployer to use Harmony RMI Registry provider for JNDI
• #Harmony configuration
  • #Use DRLVM
• #Other issues

...

With other versions and in a different environment, the behavior may differ.

Unresolved issues

Here's the brief summary of all the unresolved issues that require attention:

• HARMONY-5191 – Harmony doesn't have SSL implementation (investigated, workarounded).

• GERONIMO-3757 – Geronimo uses JKS keystore that Harmony doesn't support (investigated, workarounded).

• Web interface and console don't work through HTTP (uninvestigated, workarounded).

• Application takes up all the CPU resources on both cores I have available so the machine is 100% busy (uninvestigated).

• Application takes up all the memory specified in -Xms option (uninvestigated).

• Application fails to terminate properly – pressing Ctrl-C starts shutdown process that is never finished (uninvestigated).

Geronimo configuration

Configure the server to use Harmony RMI Registry provider for JNDI

...

Web interface and console only works work through HTTPS port (https://localhost:8443/). When working through HTTP port (http://localhost:8080/) large portions of interface are not drawn correctly. This is still to be investigated.

...

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

• Application takes up all the CPU resources on both cores I have available so the machine is 100% busy.

...

.