I have been able to workaround these two issues by setting properties.
1A) But should these properties be dynamically set relative to the named instance directory instead of GERONIMO_HOME?
1B) Or do we require the user to explicitly set these in the environment in order to start a named instance?
2) Does setting karaf.home in GERONIMO_OPTS as relative to the named instance directory instead of GERONIMO_HOME potentially cause any other issues?
To produce these issues follow these steps:
1. Unpack the latest Geronimo javaee6 bundle as /opt/geronimo3
2. Create a Geronimo named instance directory as /opt/geronimo3/gserv1
3. Move the directories var, etc, and repository into /opt/geronimo3/gserv1
4. Use this start script
On startup, the `bin/geronimo` startup script sets GERONIMO_TMPDIR explicitly as
$GERONIMO_HOME/var/temp , but the actual temp directory is really
It does not account for the cases where an instance is being started.
The workaround is to specifically specify GERONIMO_TMPDIR in your environment
before starting the instance.
On startup, the `bin/geronimo` script sets karaf.home explicitly as
$GERONIMO_HOME . Karaf expects to use
time a shell session is started (See:
The setting of the karaf.home property in `bin/geronimo` does not account for
the cases where a Geronimo named instance is being started.
The workaround is to set karaf.home in GERONIMO_OPTS before starting the instance.