Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <32984823.1225924311009.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 5 Nov 2008 16:31:51 -0600 (CST)
From: "Michael Johns (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-1963) Problems running multiple
 instances in Tomcat
In-Reply-To: 
 <31380451.1225921551043.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153185#action_153185 ] 

Michael Johns commented on CONTINUUM-1963:
------------------------------------------

The kind I mentioned earlier.  Administration pains, for one.  We don't want everyone to have all permissions, but we need each team to have the ability to set their own schedules, for example.  That leads to a person on one team potentially screwing up the schedule for a person on another team.  But the biggest problem is the single-threaded builds.  There are times when a team needs to build immediately (to do a release, for example), and currently they have to wait for the entire queue to clear, which could take a few hours (since every team has projects in the queue).

The way our organization is structured, it just doesn't make sense to share one instance of Continuum between completely unrelated projects.

> Problems running multiple instances in Tomcat
> ---------------------------------------------
>
>                 Key: CONTINUUM-1963
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1963
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.2
>         Environment: Continuum 1.2.2 web archive (not standalone)
> Tomcat 6.0.18
>            Reporter: Michael Johns
>
> I'm trying to run multiple instances of apache-continuum-1.2.2.war in a single Tomcat container.  I've got it up and running just fine, but there are a few areas where the instances overlap that prevent me from actually using them.
> 1. By default, the values from the "Configuration" page on the GUI are saved to continuum.xml in the ${appserver.base}/conf directory.  This is a problem because all instances want to share that same file.  That means all instances try to share working directories, which is very bad.  I tracked down this value in the WEB-INF/classes/META-INF/continuum directory of the web archive, but changing it there did no good.  Then I found it in the spring-context.xml file within the META-INF directory of the continuum-configuration-1.2.2.jar file that's within the WEB-INF/lib directory of the main web application.  Updating it in that file did the trick.  But now I need a separate web archive for each of my instances, which is what I was trying to avoid in the first place.
> 2. The values on the "Appearance" page are saved in a continuum-appearance.xml file that also lives in the ${appserver.base}/conf directory.  Unfortunately, the path to this file is hard-coded in the DefaultAppareanceConfiguration implementation.  The location of this config file should really come out of config as well.  Fortunately I don't care too much if each of my instances has the same footer.
> There needs to be a way to override the default configuration directory per instance without having to dig two libraries deep into the web archive.  As far as I can tell, this is the only thing preventing me from cleanly running N Continuum instances in parallel.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira