HomeDocumentation > User's guide > Troubleshooting > Runtime issues

Troubleshooting runtime issues

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.


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

Another common problem related to Java is that, sometimes, certain environment variables are not defined at Java installation time. For instance, Geronimo requires JAVA_HOME and JRE_HOME to be defined before running the server. As a convenience, make sure you also add <java_home>/bin directory to the system PATH.

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:

Service Port
SMTPPort 25
COSNamingPort 1050
NamingPort 1099
ORBSSLPort 2001
OpenEJBPort 4201
ORBPort 6882
AJPPort 8009
HTTPPort 8080
HTTPSPort 8443
JMXPort 9999
ActiveMQStompPort 61613
ActiveMQPort 61616

If you identify port conflicts you can use the <geronimo_home>/var/config/config-substitutions.properties to change any of these ports. From this configuration file you can also set a port offset and have all these increased by that amount.

Keep also in mind that personal firewalls, anti virus and spyware protection products may block some of these ports as well, even if you turn off such software sometimes those "rules" are still in effect.

Refer to the Installation and configuration section for additional details on prerequisites and different configurations.

Spring version conflicts

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:

Administration console unaccessbile by HTTPs in Internet Explorer 6

If you navigate your browser Internet Explorer (IE) 6 to the console via https://_hostname_:8443/console where hostname is replaced with the host name where the Geronimo server is running, you will get an error "The page cannot be displayed". To remedy this problem, click Tools->Internet Options, and select the Advanced tab. In the Security section, select the checkbox TLS 1.0, and you will be prompted with a Security Alert. Click Yes to view the administrative console. If you want to see information about the certificate, click View Certificate. If you want IE to accept WASCE CA permanently, you can install the certification in IE.