geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell E Glaue (Commented) (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6270) Re-enable multiple instances support in one installation
Date Tue, 14 Feb 2012 18:09:59 GMT


Russell E Glaue commented on GERONIMO-6270:

Here is a summary of the problems I am aware of in enabling multiple instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring to exist,
and will complain if it does not, however, the geronimo instance will continue to start regardless.
If it cannot create the directory, Geronimo will fail to start with the following error when
"Loading agent-car-jmx": ERROR [SnapshotConfigXMLBuilder] Could not make the directory /opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is specified relative
to the working directory the user starts up the geronimo instance. Also, if ActiveMQ cannot
create var/activemq Geronimo will fail to start with the following error when "Loading activemq-broker-blueprint":
ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason:
Failed to create directory 'var/activemq'
# GERONIMO_TMPDIR: GERONIMO-5987 (reported in comment) - The start script sets the temp directory
relative to GERONIMO_HOME, but instead should be set relative to the Geronimo Instance directory
# Karaf: GERONIMO-6174 - Karaf expects to use {karaf.home}/etc/shell.init.script each time
a shell session is started, but I think ideally that should be {karaf.base}/etc/shell.init.script
# Repository: GERONIMO-6175 - The repository will use one in {org.geronimo.server.dir}/repository
if configured, but some Geronimo code still expects a writable repository to exist at GERONIMO_HOME/repository.
If it does not exist, Geronimo will fail to start with the following errors when "Loading
rmi-naming": (1) WARN  [RMIRegistryService] RMI Registry failed, (2) ERROR [GBeanInstanceState]
Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car,j2eeType=GBean,name=RMIRegistry"

To see some of the complaints, the var directory must be removed from GERONIMO_HOME, and in
its place you must create a file named var. This will prevent Geronimo from creating GERONIMO_HOME/var
when it discovers it does not exist.

Here is the procedure to create two geronimo instances:
# Follow steps in
# Use the below start script
# create an empty file GERONIMO_HOME/var
# To expose some issues, comment out the work-arounds and restart.

Here is a start script I use to workaround some, but not all, of the issues as we are able.

# Geronimo Named Instance start script
# instance: gserv1

# Uncomment this to explicitly set Geronimo's runtime Java

# Set the location of the Geronimo Installation, and Geronimo Instance

# The Next section works around some known issues

# Must change to the server directory in order to work around ActiveMQ lock
# file conflict issue reported in GERONIMO-5987.
cd ${GSERV}

# Uncomment for the Workaround of issues in GERONIMO-6174

# This Section starts the Geronimo Instance
export GERONIMO_OPTS="${GERONIMO_OPTS} -Dorg.apache.geronimo.server.dir=${GSERV}"
# Uncomment for Normal startup, and comment out the "Interactive startup"
# Interactive startup
${GHOME}/bin/geronimo run

> Re-enable multiple instances support in one installation
> --------------------------------------------------------
>                 Key: GERONIMO-6270
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 3.0-beta-1
>            Reporter: Forrest Xia
>            Assignee: Yi Xiao
> We need to investigate how to re-enable the multiple instances support in one installation.
> Refer to 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message