incubator-wadi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Genender <jgenen...@apache.org>
Subject Re: [wadi-dev] tomcat startup simplification
Date Mon, 19 Dec 2005 14:07:36 GMT
Lets take this over to Apache please...

Bill Dudney wrote:
> Hi Jules,
> 
> Agreed that we need a way to generalize the way containers are started.
> Cargo provides a great way to do that. If we are interested I'm sure we
> could get all the support we need from the cargo team to make that happen.
> 
> Thoughts?
> 
> Just to make sure that I communicated things properly, what this change
> does is to remove the wadi-web.xml file from the web app. All that
> configuration stuff is now in the jar files (general stuff in wadi-core,
> tc55 specific stuff in the wadi-tc55 jar). The shell variables are
> simply a convenience for starting tomcat. Agreed we don't want to make
> these values have to be stored in multiple places, IMO that is where
> Cargo comes in.
> 
> TTFN,
> 
> -bd-
> 
> 
> On Dec 19, 2005, at 2:51 AM, Jules Gosnell wrote:
> 
>> Bill,
>>
>> What we need are different mechanisms for hooking the different ways
>> of starting the various container to the same configurations,
>> otherwise we are going to end up with the property set for e.g. 'red'
>> defined in several different locations/formats - this can only lead to
>> divergence and confusion.
>>
>> I'm not sure how Jan has rigged up the jetty6 plugin stuff, but I hope
>> that it reads the conf/node.red.properties file - Jan, is this the case ?
>>
>> Jan, Bill, everyone:
>>
>> does anyone have a suggestion for how this information might best be
>> stored so that it is available to e.g. maven, node.sh and standalone
>> containers ? as well as being human readable ?
>>
>> I am thinking either properties or xml...
>>
>>
>> Jules
>>
>>
>> Bill Dudney wrote:
>>
>>> Hi All,
>>>
>>> I did some more tomcat research and came up with the following
>>> scheme  to do some manual testing.
>>>
>>> I have JAVA_OPTS_RED defined like this;
>>>
>>> export JAVA_OPTS_RED="-Dwadi.home=/Users/bdudney/Development/wadi -
>>> Dwadi.version=2.0M1 -Dnode.name=red -Dhttp.port=8080 -Dajp.port=8009
>>> - Djndi.port=1099 -DSTOP.PORT=8040"
>>>
>>> I then set JAVA_OPTS to JAVA_OPTS_RED;
>>>
>>> export JAVA_OPTS=$JAVA_OPTS_RED
>>>
>>> Then I start tomcat with;
>>>
>>> bin/startup.sh -config conf/server-wadi.xml (attached)
>>>
>>> Then you can change JAVA_OPTS to JAVA_OPTS_GREEN, PINK whatever
>>> (I've  defined 5 of them in my ~/.bash_profile file) and you can
>>> start  multiple instance of tomcat using this server-wadi.xml file.
>>> Using  this i'm able to fire up 3 or 4 tomcat instances and make sure
>>> that  at least the simple stuff is working.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> <Server port="${STOP.PORT}" shutdown="SHUTDOWN">
>>>
>>>  <GlobalNamingResources>
>>>    <!-- Used by Manager webapp -->
>>>    <Resource name="UserDatabase" auth="Container"
>>>              type="org.apache.catalina.UserDatabase"
>>>       description="User database that can be updated and saved"
>>>           factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
>>>          pathname="conf/tomcat-users.xml" />
>>>  </GlobalNamingResources>
>>>
>>>  <Service name="Catalina">
>>>    <Connector port="${http.port}" maxHttpHeaderSize="8192"
>>>               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>>>               enableLookups="false" redirectPort="8443"
>>> acceptCount="100"
>>>               connectionTimeout="20000" disableUploadTimeout="true" />
>>>
>>>    <Connector port="${ajp.port}" protocol="AJP/1.3" />
>>>
>>>    <Engine name="Catalina" defaultHost="localhost">
>>>      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
>>>             resourceName="UserDatabase" />
>>>
>>>      <Host name="localhost" appBase="webapps"
>>>       unpackWARs="true" autoDeploy="true"
>>>       xmlValidation="false" xmlNamespaceAware="false">
>>>     <Context path="/wadi"                
>>> docBase="${wadi.home}/modules/webapp/target/wadi-webapp-${wadi.version}.war">
>>>
>>>       <Manager className="org.codehaus.wadi.tomcat55.TomcatManager"/>
>>>     </Context>
>>>
>>>      </Host>
>>>    </Engine>
>>>     </Service>
>>> </Server>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Improvements welcome. I'll put this into our wiki or wherever once 
>>> its settled in.
>>>
>>> This assumes that you have copied all the jar files into the proper 
>>> spots as outlined in the Nov 30th email.
>>>
>>> TTFN,
>>>
>>> -bd-
>>
>>
>>
>> --"Open Source is a self-assembling organism. You dangle a piece of
>> string into a super-saturated solution and a whole operating-system
>> crystallises out around it."
>>
>> /**********************************
>> * Jules Gosnell
>> * Partner
>> * Core Developers Network (Europe)
>> *
>> *    www.coredevelopers.net
>> *
>> * Open Source Training & Support.
>> **********************************/
>>

Mime
View raw message