Page History

...

• #Geronimo configuration
  • #Adjust {{config.xml}} to use Harmony RMI Registry provider for JNDI
  • #Customize the server startup
  • #Configure Deployer to use Harmony RMI Registry provider for JNDI
• #Harmony configuration
  • #Use DRLVM

...

<gbean name="NamingProperties">
<attribute name="namingFactoryInitial">org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory</attribute>
<attribute name="namingFactoryUrlPkgs">org.apache.harmony.jndi.provider</attribute>
<attribute name="namingProviderUrl">rmi://${ServerHostname}:${NamingPort + PortOffset}</attribute>
</gbean>

Customize the server startup

You may either edit the Geronimo startup scripts or run the server from the command line, but in either case you should make the following adjustments:

1. Harmony doesn't accept the -javaagent option, so you have to omit it.

2. Geronimo v2.0.2 needs access to Internet for applications like SPECjAppServer2004 to be deployed – it tries to fetch XML schemas from http://java.sun.com site. So if you're going to deploy applications like that, and you're behind a firewall, you should add the appropriate -Dhttp.proxyHost= and -Dhttp.proxyPort= options to the Geronimo command line. This problem is caused by OPENEJB-700 bug and should disappear after that bug is fixed and the fix is propagated to a new version of Geronimo.

So, your final startup line may look like this:

Configure Deployer to use Harmony RMI Registry provider for JNDI

...