Optimize Geronimo 3.0

Tuesday, 10 April 2012 07:59 Written by Sébastien Dante Ursini

If you want to optimize the boot time of your Geronimo Application Server you can disable several components but you need to define precisely your needs. If you don't need ActiveMQ, UDDI, Apache Aries and Apache Wink you can save between 25% and 30% of the boot time.�

I don't need Active MQ

Using your administration console in user assets -> Web Apps you can stop the following web application :

org.apache.geronimo.plugins/activemq-console-tomcat/3.0-beta-1/car

You can stop the ActiveMQ Broker blueprint in resources -> System modules :

org.apache.geronimo.configs/activemq-broker-blueprint/3.0-beta-1/car

I don't need UDDI

Even if you are using Web Services you have no need for the general service that provide UDDI. UDDI (Universal Description Discovery and Integration)  is an XML based registry for for businesses worldwide to list themselves on the Internet and a mechanism to register and locate web service applications.

Using your administration console in user assets -> Web Apps you can stop the uddi-tomcat web application :

org.apache.geronimo.configs/uddi-tomcat/3.0-beta-1/car

You can stop the UDDI J2ee connection  in applications -> User Assets -> Java EE Connectors :

org.apache.geronimo.plugins/uddi-db/3.0-beta-1/car

I don't need Apache Aries

You can stop the Apache Wink modules in resources -> System modules :

org.apache.geronimo.configs/wink/3.0-beta-1/car
org.apache.geronimo.configs/wink-deployer/3.0-beta-1/car   

I don't need Apache Wink

�

You can stop the Apache Wink modules in resources -> System modules :

�

 
org.apache.geronimo.configs/wink/3.0-beta-1/car
org.apache.geronimo.configs/wink-deployer/3.0-beta-1/car   
 

Let me know if you can share other interesting tips to improve boot time or speed of your favorite Application Server.

Sébastien Dante Ursini

Sébastien�Dante�Ursini

Java Specialist
15 Years of experience in Java
Based in Geneva/Switzerland