Page History

...

Most of the issues you may find when running Geronimo will be at start up time; and most likely driven by some conflicting resources from the environment where Geronimo is set up.

...

JVM arguments

Apache Geronimo v2.2 is Java EE certified. With that said, it will likely run on different JVM versions however the results may be unpredictable. Whenever possible use jdk 1.5 or above.

...

1. startup.sh or geronimo.sh run
   • set JAVA_OPTS environment variable: No FormatborderStylesolid jeffchi@Local:~/geronimo-tomcat6-javaee5-2.2-SNAPSHOT$ export JAVA_OPTS="-Xmx256m -XX:MaxPermSize=128m -XX:+HeapDumpOnOutOfMemoryError" jeffchi@Local:~/geronimo-tomcat6-javaee5-2.2-SNAPSHOT$./bin/geronimo.sh run
   • and/or append the following code to <Geronimo_Home>/bin/setjavaenv.sh(bat) file: Code Block if [ -z "$JAVA_OPTS" ]; then JAVA_OPTS="-Xmx256m -XX:MaxPermSize=128m -XX:+HeapDumpOnOutOfMemoryError" fi
2. start-server or gsh geronimo/start-server
   • edit <Geronimo_Home>/etc/rc.d/start-server,default.groovy file: Code Block // Append some reasonable java flags if none were configured already if (command.javaFlags.empty) { command.javaFlags << '-Xmx256m' command.javaFlags << '-XX:MaxPermSize=128m' command.javaFlags << '-XX:+HeapDumpOnOutOfMemoryError' }
   • or use -J flag: No FormatBorderStyleSolid jeffchi@Local:~/geronimo-tomcat6-javaee5-2.2-SNAPSHOT$./bin/gsh geronimo/start-server -J "-Xmx256m -XX:MaxPermSize=128m -XX:+HeapDumpOnOutOfMemoryError"

Port conflicts

The second most common startup issue is associated to port conflicts, check no other application is using or blocking Geronimo's default ports:

...

If your application contains its own version of Spring you might see some problems deploying or running the application on the Jetty assembly. The Jetty assembly is by default configured with Apache CXF as the JAX-WS provider. Apache CXF uses Spring to configure itself. Sometimes, the Spring version used by CXF conflicts with the Spring version supplied with your application. To prevent these conflicts add the following <hidden-classes> entry to the Geronimo deployment descriptor:

...

...

java.lang.UnsatisfiedLinkError: lic (Library is already loaded in another ClassLoader)

...

java.io.IOException of remote EJB on Windows

...

One possibility is that the available user port numbers are being exhausted. On Windows, when a socket is closed, it goes into a TIME_WAIT state and isn't actually closed until some delay time. By default, the max user port address is 5000 and the TIME_WAIT delay is 4 minutes. So, it's not too difficult to exhaust all possible user port addresses.

...

Most likely Geronimo server was not shut down cleanly, which results in ActiveMQ log files to have an unexpected entry. You can avoid this by editing var/activemq/conf/activemq.xml and adding schedulerSupport="false" if you don't require JobScheduler support:

...

...