You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Michael Johns (JIRA)" <ji...@codehaus.org> on 2008/11/05 22:45:51 UTC
[jira] Created: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
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
[jira] Updated: (CONTINUUM-1963) appserver.base should be
configurable for the webapp without a system property
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1963:
------------------------------------
Summary: appserver.base should be configurable for the webapp without a system property (was: Problems running multiple instances in Tomcat)
> appserver.base should be configurable for the webapp without a system property
> ------------------------------------------------------------------------------
>
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153182#action_153182 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
I should have noted that what you proposed is actually how we're doing it today. And it's causing pains, so we want to split the instances.
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153177#action_153177 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
We have four separate projects that use Continuum, and we want to leverage one piece of hardware. Everything about these projects is separate, so we want them all in separate instances of Continuum. Even though I could, I don't really want to run four separate instances of Tomcat. I should simply be able to run the same web application four times within the same Tomcat. And in fact I can, except for these two problems.
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154064#action_154064 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
One easy way to fix this (and perhaps some other Continuum issues) is to put a CONFIG table in the database that just holds name/value pairs. I say that will the full understanding that I'm no expert on the Continuum data model or best practices, so I don't know if that's a feasible solution or not. But it would solve the problem by taking the contention off of the file system. You could even put a "logDir" value in there and then put it on the config page with the rest of the directory configurations.
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153466#action_153466 ]
Wendy Smoak commented on CONTINUUM-1963:
----------------------------------------
Is there an issue open for the problem with it using the same log file?
(It would probably be better to break this up into individual issues and move this discussion on the dev list.)
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153456#action_153456 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
One more thing is the location of continuum.log. That's currently configured in WEB-INF/classes/log4j.xml. Without a change, all instances log to the same file, which gets very confusing.
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173752#action_173752 ]
Brett Porter commented on CONTINUUM-1963:
-----------------------------------------
with per-group administration capabilities and parallel builds in 1.3.2, I'm not sure if this is necessary any more.
However, this issue amounts to making appserver.base configurable for the webapp without a system property which I think is a good thing, so I'll adjust the subject
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153184#action_153184 ]
Olivier Lamy commented on CONTINUUM-1963:
-----------------------------------------
What kind of pains ?
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153668#action_153668 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
I haven't seen an open issue for the log file contention. We can break this issue up if you think that's best, though it really all falls under the umbrella of not being able to run multiple instances concurrently. I'd hate for some of the contention to be fixed but not all of it.
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153179#action_153179 ]
Olivier Lamy commented on CONTINUUM-1963:
-----------------------------------------
You can certainly add all your projects in the same continuum instance.
Why can't you do it ?
> 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
[jira] Updated: (CONTINUUM-1963) appserver.base should be
configurable for the webapp without a system property
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-1963:
-----------------------------------
Fix Version/s: Reviewed
> appserver.base should be configurable for the webapp without a system property
> ------------------------------------------------------------------------------
>
> 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
> Fix For: Reviewed
>
>
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153180#action_153180 ]
Michael Johns commented on CONTINUUM-1963:
------------------------------------------
Yes, that's an option, but for housekeeping, we didn't want to do that. We need each team lead to be an admin in Continuum, but we don't want them messing with projects on other teams. And an even bigger issue is that each team needs to wait for the other teams' builds right now. We want to eliminate that backlog and allow each team to build whenever they want, without having to wait (or even worse, manually clear the queue).
> 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
[jira] Commented: (CONTINUUM-1963) Problems running multiple
instances in Tomcat
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153175#action_153175 ]
Olivier Lamy commented on CONTINUUM-1963:
-----------------------------------------
What is your use case to do such configuration ?
> 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