Running many Geronimo instances on the same machine can lead to port conflicts. You can assign new port numbers to services per Geronimo instance or disable them completely so they are not started up. Let's see what needs to be done in order to disable Geronimo services.

Let say you want to disable the ActiveMQ brokers. Their configuration in var/config/config.xml file is as follows (Geronimo 2.1-SNAPSHOT):

When you run Geronimo these services (gbeans) are shown in the Listening on Ports section at Geronimo startup:

The services in question are two ActiveMQ Transport Connectors listening to 61613 and 61616 ports.

To disable these two ActiveMQ Transport Connectors you need to disable ActiveMQ.tcp.default and ActiveMQ.stomp.default gbeans. Edit var/config/config.xml and add the attribute load="false" in their gbean definitions. Note the load="false" attributes of the ns2:gbean elements.

After the change, when you start up Geronimo it will show you that the gbeans are indeed not started.

You do need to be very careful with disabling Geronimo services as some other services can still rely on them and as far as the ActiveMQ services go the following exception might be thrown: