install on tomcat 5.5

[mffortin]

Hello,
I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other than
setting up the Manager element in the server.xml I'm at a loss as to how
to figure it.  Is there a way to setup wadi's config properties
(node.name, etc.) inside the Manager element?  Or alternately, how does
the manager pick up the node.properties and if I have many hosts with
their own manager (different cluster group for each host) how does it
find the correct properties?
 
When can I expect the documentation on how to install wadi to be
published to the site?

I for one am eagerly awaiting a final release, it certainly would fill a
gap for us..

Thanks

--
Michael Fortin



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Jules Gosnell-4]

Michael Fortin wrote:
> Hello,

Hi, Michael,

> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other than
> setting up the Manager element in the server.xml I'm at a loss as to how
> to figure it.  Is there a way to setup wadi's config properties
> (node.name, etc.) inside the Manager element?

Have you walked through the 'getting started' doc ?

http://wadi.codehaus.org/getting-started/index.html


> Or alternately, how does
> the manager pick up the node.properties and if I have many hosts with
> their own manager (different cluster group for each host) how does it
> find the correct properties?

If you take a look at the way that we start TC from the node.sh script :

http://svn.wadi.codehaus.org/browse/~raw,r=2010/wadi/trunk/wadi/wadi-assembly/src/bin/node.sh

node.sh reads the <colour>.properties file and puts its contents onto a
variable that is passed to the jvm at startup. Other properties are also
passed in this way to handle logging etc.

If you want to run WADI in from a standard TC55 installation, it will
involve the copying of the jars that node.sh places on the classpath
into e.g. server/lib, as well as passing in (some of) these properties
somehow.

Some of the properties are consumed in our Tomcat server.xml (e.g. port
numbers), and some are consumed by the WEB-INF/wadi-web.xml. There may
still be a couple of references to the props in the code itself - but
these should not be there. Everything that WADI needs should be injected
by Spring.

>
> When can I expect the documentation on how to install wadi to be
> published to the site?

Well - we are talking about sorting out some documentation at the
moment. If you confirm that your goal is to get WADI running in a
Vanilla TC55 install, I will write up some notes on this over the next
couple days and let you have a copy. If you would be kind enough to walk
through them and report on any ommissions/inaccuracies, I would greatly
appreciate it.

> I for one am eagerly awaiting a final release, it certainly would fill a
> gap for us..

Well - we have a way to go - let us know the features that you are
particularly interested in and I shall see what I can do ...

Thanks for your interest in WADI,


Jules

>
> Thanks
>


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Jules Gosnell-4]

Michael Fortin wrote:

> Hello,
> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other than
> setting up the Manager element in the server.xml I'm at a loss as to how
> to figure it.  Is there a way to setup wadi's config properties
> (node.name, etc.) inside the Manager element?  Or alternately, how does
> the manager pick up the node.properties and if I have many hosts with
> their own manager (different cluster group for each host) how does it
> find the correct properties?
>
> When can I expect the documentation on how to install wadi to be
> published to the site?
> I for one am eagerly awaiting a final release, it certainly would fill a
> gap for us..
>
> Thanks
>

just got this going on 5.5.17 and svn TRUNK this evening - bear with me
for a couple more days and I will document the installation on a vanilla
5.5.17 and release a snapshot...

Jules


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[mffortin]

Hi Jules,

Thanks for putting in the time to put the docs together, I can image
your time is precious.  I'm really busy with a new site right now, as
usual it's feast or famine for me, as far as work goes, but I'll be able
to do more testing by the time you have some updated docs.  

As to your previous response I will gladly report on my experiences with
the install as soon as I can.

thanks again

Michael Fortin



Jules Gosnell wrote:

> Michael Fortin wrote:
>> Hello,
>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other
>> than setting up the Manager element in the server.xml I'm at a loss
>> as to how to figure it.  Is there a way to setup wadi's config
>> properties (node.name, etc.) inside the Manager element?  Or
>> alternately, how does the manager pick up the node.properties and if
>> I have many hosts with their own manager (different cluster group for
>> each host) how does it find the correct properties?
>>
>> When can I expect the documentation on how to install wadi to be
>> published to the site?
>> I for one am eagerly awaiting a final release, it certainly would
>> fill a gap for us..
>>
>> Thanks
>>
>
> just got this going on 5.5.17 and svn TRUNK this evening - bear with
> me for a couple more days and I will document the installation on a
> vanilla 5.5.17 and release a snapshot...
>
> Jules
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[mffortin]

Hi Jules,

I tried to get the samples running but I ran into some issues with
paths.  At work I only have windows xp with cygwin to use so I tried to
change some of the paths in the node.sh.  It fails when it tries to
install the wars. Where does the path for the contextConfig come from?  
I'd like to try to alter that path as well to see if I can get the
examples running.

$ ./node.sh tomcat55 red
JAVA_HOME=c:\PROGRA~1\Java\JDK15~1.0
WADI_HOME=/cygdrive/c/java/wadi-2.0M2-SNAPSHOT/bin/..
WADI_VERSION=2.0M2-SNAPSHOT
java full version "1.5.0_02-b09"
rm: cannot remove directory
`/cygdrive/c/java/wadi-2.0M2-SNAPSHOT/bin/../tmp/red/conf': Device or
resource busy
TOMCAT55_HOME=/cygdrive/c/java/apache-tomcat-5.5.17
2006/09/21 14:24:44:685 EDT [INFO] Http11BaseProtocol - Initializing
Coyote HTTP/1.1 on http-8080
2006/09/21 14:24:44:685 EDT [INFO] Catalina - Initialization processed
in 1125 ms
2006/09/21 14:24:44:748 EDT [WARN] MemoryUserDatabase - User database is
not persistable - no write permissions on directory
2006/09/21 14:24:44:763 EDT [INFO] StandardService - Starting service
Catalina
2006/09/21 14:24:44:763 EDT [INFO] StandardEngine - Starting Servlet
Engine: Apache Tomcat/5.5.17
2006/09/21 14:24:44:779 EDT [INFO] StandardHost - XML validation disabled
2006/09/21 14:24:44:795 EDT [ERROR] ContextConfig - Exception fixing
docBase: {0}  <java.io.IOException: Application base directory
C:\cygdrive\c\java\wadi-2.0M2-SNAPSHOT\tmp\red\
webapps does not exist>java.io.IOException: Application base directory
C:\cygdrive\c\java\wadi-2.0M2-SNAPSHOT\tmp\red\webapps does not exist
        at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:121)
        at
org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:868)
        at
org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:980)
        at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:278)
        at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5130)
        at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3945)
        at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at
org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at
org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at
org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)

2006/09/21 14:24:44:873 EDT [ERROR] StandardContext - Error starting
static Resources <java.lang.IllegalArgumentException: Invalid or
unreadable WAR file : C:\cygdrive\c\java\wadi
-2.0M2-SNAPSHOT\tmp\red\webapps\cygdrive\c\java\wadi-2.0M2-SNAPSHOT\bin\..\webapps\wadi-webapp-2.0M2-SNAPSHOT.war>java.lang.IllegalArgumentException:
Invalid or unreadable WAR fil
e :
C:\cygdrive\c\java\wadi-2.0M2-SNAPSHOT\tmp\red\webapps\cygdrive\c\java\wadi-2.0M2-SNAPSHOT\bin\..\webapps\wadi-webapp-2.0M2-SNAPSHOT.war
        at
org.apache.naming.resources.WARDirContext.setDocBase(WARDirContext.java:129)
        at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3814)
        at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3985)
        at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at
org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at
org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at
org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)

2006/09/21 14:24:44:935 EDT [ERROR] StandardContext - Error in
resourceStart()
2006/09/21 14:24:45:060 EDT [ERROR] StandardContext - Error getConfigured
2006/09/21 14:24:45:060 EDT [ERROR] StandardContext - Context [/wadi]
startup failed due to previous errors
2006/09/21 14:24:45:060 EDT [INFO] StandardContext - Container
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/wadi]
has not been started
2006/09/21 14:24:45:138 EDT [INFO] Http11BaseProtocol - Starting Coyote
HTTP/1.1 on http-8080
2006/09/21 14:24:45:310 EDT [INFO] ChannelSocket - JK: ajp13 listening
on /0.0.0.0:8009
2006/09/21 14:24:45:326 EDT [INFO] JkMain - Jk running ID=0 time=0/31  
config=null
2006/09/21 14:24:45:341 EDT [INFO] StoreLoader - Find registry
server-registry.xml at classpath resource
2006/09/21 14:24:45:404 EDT [INFO] Catalina - Server startup in 719 ms
2006/09/21 14:25:03:170 EDT [INFO] Http11BaseProtocol - Pausing Coyote
HTTP/1.1 on http-8080

Michael Fortin





Michael Fortin wrote:

> Hi Jules,
>
> Thanks for putting in the time to put the docs together, I can image
> your time is precious.  I'm really busy with a new site right now, as
> usual it's feast or famine for me, as far as work goes, but I'll be
> able to do more testing by the time you have some updated docs.  
> As to your previous response I will gladly report on my experiences
> with the install as soon as I can.
>
> thanks again
>
> Michael Fortin
>
>
>
> Jules Gosnell wrote:
>> Michael Fortin wrote:
>>> Hello,
>>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other
>>> than setting up the Manager element in the server.xml I'm at a loss
>>> as to how to figure it.  Is there a way to setup wadi's config
>>> properties (node.name, etc.) inside the Manager element?  Or
>>> alternately, how does the manager pick up the node.properties and if
>>> I have many hosts with their own manager (different cluster group
>>> for each host) how does it find the correct properties?
>>>
>>> When can I expect the documentation on how to install wadi to be
>>> published to the site?
>>> I for one am eagerly awaiting a final release, it certainly would
>>> fill a gap for us..
>>>
>>> Thanks
>>>
>>
>> just got this going on 5.5.17 and svn TRUNK this evening - bear with
>> me for a couple more days and I will document the installation on a
>> vanilla 5.5.17 and release a snapshot...
>>
>> Jules
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Jules Gosnell-4]

Michael Fortin wrote:
> Hi Jules,
>
> Thanks for putting in the time to put the docs together, I can image
> your time is precious.  I'm really busy with a new site right now, as
> usual it's feast or famine for me, as far as work goes, but I'll be able
> to do more testing by the time you have some updated docs.  
> As to your previous response I will gladly report on my experiences with
> the install as soon as I can.

great - I'll put something together for you,

Jules

>
> thanks again
>
> Michael Fortin
>
>
>
> Jules Gosnell wrote:
>
>> Michael Fortin wrote:
>>
>>> Hello,
>>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other
>>> than setting up the Manager element in the server.xml I'm at a loss
>>> as to how to figure it.  Is there a way to setup wadi's config
>>> properties (node.name, etc.) inside the Manager element?  Or
>>> alternately, how does the manager pick up the node.properties and if
>>> I have many hosts with their own manager (different cluster group for
>>> each host) how does it find the correct properties?
>>>
>>> When can I expect the documentation on how to install wadi to be
>>> published to the site?
>>> I for one am eagerly awaiting a final release, it certainly would
>>> fill a gap for us..
>>>
>>> Thanks
>>>
>>
>> just got this going on 5.5.17 and svn TRUNK this evening - bear with
>> me for a couple more days and I will document the installation on a
>> vanilla 5.5.17 and release a snapshot...
>>
>> Jules
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Jules Gosnell-4]

Jules Gosnell wrote:

> Michael Fortin wrote:
>
>> Hi Jules,
>>
>> Thanks for putting in the time to put the docs together, I can image
>> your time is precious.  I'm really busy with a new site right now, as
>> usual it's feast or famine for me, as far as work goes, but I'll be
>> able to do more testing by the time you have some updated docs.  As to
>> your previous response I will gladly report on my experiences with the
>> install as soon as I can.
>
>
> great - I'll put something together for you,

still working on this - had a classloading issue, which is now fixed,
but now seeing something wrong in a filter startup. will take care of
this ASAP, get fixes into svn and then give you something to play with.

Jules

>
> Jules
>
>>
>> thanks again
>>
>> Michael Fortin
>>
>>
>>
>> Jules Gosnell wrote:
>>
>>> Michael Fortin wrote:
>>>
>>>> Hello,
>>>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other
>>>> than setting up the Manager element in the server.xml I'm at a loss
>>>> as to how to figure it.  Is there a way to setup wadi's config
>>>> properties (node.name, etc.) inside the Manager element?  Or
>>>> alternately, how does the manager pick up the node.properties and if
>>>> I have many hosts with their own manager (different cluster group
>>>> for each host) how does it find the correct properties?
>>>>
>>>> When can I expect the documentation on how to install wadi to be
>>>> published to the site?
>>>> I for one am eagerly awaiting a final release, it certainly would
>>>> fill a gap for us..
>>>>
>>>> Thanks
>>>>
>>>
>>> just got this going on 5.5.17 and svn TRUNK this evening - bear with
>>> me for a couple more days and I will document the installation on a
>>> vanilla 5.5.17 and release a snapshot...
>>>
>>> Jules
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Jules Gosnell-4]

Michael,

check out:

http://docs.codehaus.org/display/WADI/Tomcat+5.5

I've just checked a couple of changes in to make this work, so you will
need to svn update and bin/build.sh (or equiv - take a look inside
build.sh).

sorry it took me so long to sort this out. It wasn't as straightforward
as it should have been and I have been very short of time for the last
month or so :-(

Let me know if you have any further problems/questions and I'll try to
turn them around a little faster.

regards,


Jules




Jules Gosnell wrote:

> Jules Gosnell wrote:
>
>> Michael Fortin wrote:
>>
>>> Hi Jules,
>>>
>>> Thanks for putting in the time to put the docs together, I can image
>>> your time is precious.  I'm really busy with a new site right now, as
>>> usual it's feast or famine for me, as far as work goes, but I'll be
>>> able to do more testing by the time you have some updated docs.  As
>>> to your previous response I will gladly report on my experiences with
>>> the install as soon as I can.
>>
>>
>>
>> great - I'll put something together for you,
>
>
> still working on this - had a classloading issue, which is now fixed,
> but now seeing something wrong in a filter startup. will take care of
> this ASAP, get fixes into svn and then give you something to play with.
>
> Jules
>
>>
>> Jules
>>
>>>
>>> thanks again
>>>
>>> Michael Fortin
>>>
>>>
>>>
>>> Jules Gosnell wrote:
>>>
>>>> Michael Fortin wrote:
>>>>
>>>>> Hello,
>>>>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and other
>>>>> than setting up the Manager element in the server.xml I'm at a loss
>>>>> as to how to figure it.  Is there a way to setup wadi's config
>>>>> properties (node.name, etc.) inside the Manager element?  Or
>>>>> alternately, how does the manager pick up the node.properties and
>>>>> if I have many hosts with their own manager (different cluster
>>>>> group for each host) how does it find the correct properties?
>>>>>
>>>>> When can I expect the documentation on how to install wadi to be
>>>>> published to the site?
>>>>> I for one am eagerly awaiting a final release, it certainly would
>>>>> fill a gap for us..
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>> just got this going on 5.5.17 and svn TRUNK this evening - bear with
>>>> me for a couple more days and I will document the installation on a
>>>> vanilla 5.5.17 and release a snapshot...
>>>>
>>>> Jules
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[mffortin]

Hi Jules,

Thanks for all your work.  Here is what I did:
wadi version 2043 (svn checkout)
tomcat version 5.5.17
mac osx version 10.4.8
java version 1.5.0_06-112

- created 2 directoriess server1 and server2
~/www-wadi/server1
~/www-wadi/server2
- copied in the bin and conf directories from catalina_home
- altered the catalina.sh as fallows, with different ports and node names.

export CATALINA_HOME=/java/apache-tomcat-5.5.17
export CATALINA_BASE=/Users/michaelfortin/www-wadi/server1

# JAVA_OPTS
JAVA_OPTS="-Dhttp.port=8180 "
JAVA_OPTS="$JAVA_OPTS -Dnode.name=blue "
JAVA_OPTS="$JAVA_OPTS
-Dwadi.home=/java/wadi/wadi-assembly/target/wadi-2.0M2-SNAPSHOT-bin/wadi-2.0M2-SNAPSHOT/
"
JAVA_OPTS="$JAVA_OPTS -Dwadi.version=2.0M2-SNAPSHOT "

echo "JAVA_OPTS:    $JAVA_OPTS"


- altered my server.xml to have different http ports and shutdown ports
- copied the the listed libraries to catalina_home
- set content manager to:
<Context path="/wadi" >
    <Manager className="org.codehaus.wadi.tomcat55.TomcatManager"/>
</Context>
- I copied the wadi.war into my webapps directory




I can see a red (the other server) and a blue page with a counter on it
by calling http://localhost:8280/wad/session.jsp and
http://localhost:8180/wad/session.jsp but I'm not sure if they're
communicating.  There is nothing in the catalina.out related to wadi.  
How do I verify that they're talking?

And on a side note when I tried to run '> node.sh tomcat55 red' from the
install bin directory I get an exception

2006/10/04 20:56:35:736 EDT [ERROR] Digester - Begin event threw error
<java.lang.NoClassDefFoundError:
org/codehaus/wadi/web/WebSessionFactory>java.lang.NoClassDefFoundError:
org/codehaus/wadi/web/WebSessionFactory
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
        at java.lang.Class.getConstructor0(Class.java:2640)
        at java.lang.Class.newInstance0(Class.java:321)
        at java.lang.Class.newInstance(Class.java:303)


thanks




On Sep 28, 2006, at 7:57 PM, Jules Gosnell wrote:

> Michael,
>
> check out:
>
> http://docs.codehaus.org/display/WADI/Tomcat+5.5
>
> I've just checked a couple of changes in to make this work, so you
> will need to svn update and bin/build.sh (or equiv - take a look
> inside build.sh).
>
> sorry it took me so long to sort this out. It wasn't as
> straightforward as it should have been and I have been very short of
> time for the last month or so :-(
>
> Let me know if you have any further problems/questions and I'll try to
> turn them around a little faster.
>
> regards,
>
>
> Jules
>
>
>
>
> Jules Gosnell wrote:
>> Jules Gosnell wrote:
>>> Michael Fortin wrote:
>>>
>>>> Hi Jules,
>>>>
>>>> Thanks for putting in the time to put the docs together, I can
>>>> image your time is precious.  I'm really busy with a new site right
>>>> now, as usual it's feast or famine for me, as far as work goes, but
>>>> I'll be able to do more testing by the time you have some updated
>>>> docs.  As to your previous response I will gladly report on my
>>>> experiences with the install as soon as I can.
>>>
>>>
>>>
>>> great - I'll put something together for you,
>> still working on this - had a classloading issue, which is now fixed,
>> but now seeing something wrong in a filter startup. will take care of
>> this ASAP, get fixes into svn and then give you something to play with.
>> Jules
>>>
>>> Jules
>>>
>>>>
>>>> thanks again
>>>>
>>>> Michael Fortin
>>>>
>>>>
>>>>
>>>> Jules Gosnell wrote:
>>>>
>>>>> Michael Fortin wrote:
>>>>>
>>>>>> Hello,
>>>>>> I'm trying to setup tomcat 5.5.17 to use wadi clustering, and
>>>>>> other than setting up the Manager element in the server.xml I'm
>>>>>> at a loss as to how to figure it.  Is there a way to setup wadi's
>>>>>> config properties (node.name, etc.) inside the Manager element?  
>>>>>> Or alternately, how does the manager pick up the node.properties
>>>>>> and if I have many hosts with their own manager (different
>>>>>> cluster group for each host) how does it find the correct properties?
>>>>>>
>>>>>> When can I expect the documentation on how to install wadi to be
>>>>>> published to the site?
>>>>>> I for one am eagerly awaiting a final release, it certainly would
>>>>>> fill a gap for us..
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>> just got this going on 5.5.17 and svn TRUNK this evening - bear
>>>>> with me for a couple more days and I will document the
>>>>> installation on a vanilla 5.5.17 and release a snapshot...
>>>>>
>>>>> Jules
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>    http://xircles.codehaus.org/manage_email
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email