Hi,
In Geronimo binary install which directories do we consider read-only
vs. write/read? The idea is that the read-only directories could be
shared among multiple installations to save some space and reduce
maintenance.
Here's what I identified so far:
read-only:
- bin
- jsr88
- schema
- li
This idea is like the multiple instances feature we had in 2.1 branch, but
not supported in trunk now.
Geronimo 2.1.x support copying "var" folder to add more instances with a
same installation, but G trunk code does not support that feature now.
Do we have a user scenario to mandate that feature
If we want to continue maintain such complexity in 3.0? Hard drive is pretty
cheap nowadays.
And I think currently the part that looks a little bit wasting space is
karaf "copy" the artifacts from repository to cache when start..
-Rex
2011/9/21 Forrest Xia
> This idea is like the multiple inst
The lib directory might also need read/write, as it contains the endorsed
folder, for the bin directory, there might also be changes, as there is a
setjavaenv script files which are used to add system properties by end
users.
Not sure I understand correctly, do you mean to grant read-only permissio
AFAIK, we still have a desire to support multiple instances per Geronimo base
install.
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
We have been working towards a common configuration location in 3.0 trunk for
all parts of Geronimo.
I am expecting to test and use m
3.0 does not have the feature like the doc for multiple instances support.
The doc needs update.
Forrest
On Wed, Sep 21, 2011 at 11:03 PM, Russell E Glaue wrote:
> AFAIK, we still have a desire to support multiple instances per Geronimo
> base
> install.
>
> https://cwiki.apache.org/GMOxDOC30/r
The way by sharing the repository or certain folders is not enabled in 3.0
yet. To run multiple instances on one machine, the only way is to copy the
server folder to another place on the disk, and then start the server after
changing the offPortset value in config-substitutions.properties file.
When there are multiple instances, they do not share repositories. Each instance
must have its own copy of the repository.
That Wiki page is actually still relevant and correct. There is a note on that
page that multiple instances for the javaee6 bundle is currently not working.
That note need onl
It should be noted that as long as JIRA GERONIMO-5987 goes unresolved, even if
you install several copies of Geronimo into different file structure locations
(e.g. /opt/g1 and /opt/g2), the javaee6 bundle does not allow multiple Geronimo
servers to run within the same runtime OS.
GERONIMO-5987 is
With Rex's latest commit for GERONIMO-5987, and testing with
geronimo-tomcat7-javaee6-3.0-20110923.091022-350-bin, I am able to run multiple
instances of the Geronino javaee6 bundle now.
To make it work, you have to follow my specific startup procedure I gave in
GERONIMO-5987 which refers to an ex
Jarek,
I have been unable to locate a thread which we discussed about sharing
repositories. IIRC, there are (or were at some time) some components that wrote
back to the repository - and I am not thinking they are the applications.
Geronimo at one time was able to share repositories, probably in
Jarek,
I appreciate this discussion was started.
I am working through multiple-instance support for Geronimo, and it seems the
code is not consistent in using org.apache.geronimo.home.dir (geronimoHome) vs
org.apache.geronio.server.dir (geronimoBase).
The correct use of the two is hinted at in the
12 matches
Mail list logo
