You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Neil Aggarwal <ne...@JAMMConsulting.com> on 2003/05/13 01:11:02 UTC
Sessions not replicating
Filip:
I am trying to follow your document at
http://cvs.apache.org/~fhanik/index.html
to set-up session replication in tomcat 4.
I have two machines running apache 2.0.44 and tomcat 4.1.24 using the
mod_webapp
connector.
These two machines are on a private subnet which gets mapped
to public IP addresses. They are
gnwebapp1.gaggle.net with internal IP 192.168.0.11
gaggle5.gaggle.net with internal IP 192.168.0.5
On both servers, in the tomcat server.xml in the <Service
name="Tomcat-Apache">
tag, I added these lines:
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="false" autoDeploy="false">
<Context path="/www-test" docBase="www-test" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_reptest_log." suffix=".txt"
timestamp="true"/>
<Valve className="org.apache.catalina.session.ReplicationValve"
filter=".*\.gif;.*\.jpg;.*\.jpeg;.*\.js"
debug="0"/>
<Manager
className="org.apache.catalina.session.InMemoryReplicationManager"
debug="10"
printToScreen="true"
saveOnRestart="false"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1"
pathname="null"
printSessionInfo="true"
checkInterval="10"
expireSessionsOnShutdown="false"
serviceclass="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="228.1.2.3"
mcastPort="45566"
mcastFrequency="500"
mcastDropTime="5000"
tcpListenAddress="auto"
tcpListenPort="4001"
tcpSelectorTimeout="100"
tcpThreadCount="2"
useDirtyFlag="true">
</Manager>
</Context>
</Host>
I then started the tomcat and apache on gaggle5 and saw this output in
the localhost_reptest log:
2003-05-12 15:57:55 ContextConfig[/www-test]: Missing application web.xml,
using defaults only
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Starting
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Force random number initialization starting
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Seeding random number generator class java.security.SecureRandom
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Seeding of random number generator has been completed
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Getting message digest component for algorithm MD5
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Completed getting message digest component
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Force random number initialization completed
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Member channel started inside tomcat, version v0.998
2003-05-12 15:57:55 StandardManager[/www-test]: [InMemoryReplicationManager]
Sleeping for 5 secs to establish cluster membership
2003-05-12 15:58:00 StandardWrapper[/www-test:default]: Loading container
servlet default
2003-05-12 15:58:00 StandardWrapper[/www-test:invoker]: Loading container
servlet invoker
So, it seems that the replication manager loaded OK.
Then, I started the apache and tomcat on gnwebapp1. In is reptest log, I
saw this output:
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Starting
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Force random number initialization starting
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Seeding random number generator class java.security.SecureRandom
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Seeding of random number generator has been completed
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Getting message digest component for algorithm MD5
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Completed getting message digest component
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Force random number initialization completed
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Member channel started inside tomcat, version v0.998
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Sleeping for 5 secs to establish cluster membership
2003-05-12 15:59:00 StandardManager[/www-test]: [InMemoryReplicationManager]
Replication member
added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.0.5:4001,1
92.168.0.5,4001]
2003-05-12 15:59:05 StandardContext[/www-test]: Posting standard context
attributes
2003-05-12 15:59:05 StandardContext[/www-test]: Configuring application
event listeners
2003-05-12 15:59:05 StandardContext[/www-test]: Sending application start
events
2003-05-12 15:59:05 StandardContext[/www-test]: Starting filters
2003-05-12 15:59:05 StandardWrapper[/www-test:default]: Loading container
servlet default
2003-05-12 15:59:05 StandardWrapper[/www-test:invoker]: Loading container
servlet invoker
2003-05-12 15:59:05 StandardContext[/www-test]: Starting completed
And in the log on the gaggle5 server, I saw this information:
2003-05-12 15:58:59 StandardManager[/www-test]: [InMemoryReplicationManager]
Replication member
added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.0.11:4001,
192.168.0.11,4001]
2003-05-12 15:59:04 StandardManager[/www-test]: [InMemoryReplicationManager]
InMemoryReplicationManager.messageDataReceived(): received message
2003-05-12 15:59:04 StandardManager[/www-test]: [InMemoryReplicationManager]
Received SessionMessage of type=SESSION-GET-ALL
So, it seems that the two machines are talking to each other.
But, when I opened a browser and visited this page:
http://gaggle5.gaggle.net/www-test/index.jsp
and then went to this page:
http://gnwebapp1.gaggle.net/www-test/index.jsp
I got two different session IDs. Also, there were no additional messages in
the replication logs.
Does session replication work on servers that have apache and tomcat using
the mod_webapp connector?
Thanks,
Neil.
--
Neil Aggarwal
JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development Websites, Ecommerce, Java, databases
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Sessions not replicating
Posted by Neil Aggarwal <ne...@JAMMConsulting.com>.
Filip:
We have a radware WSD Pro loadbalancer, which is set up to use
this url to balance between the two servers:
http://www-test.gaggle.net/www-test/index.jsp
Here is what I did:
1. I loaded the page using the url above. The load balancer
put me on gnwebapp1. I noted the session ID.
2. I turned off apache on gnwebapp1.
3. I checked the status on the load balancer and waited
until it noticed that gnwebapp1 was offline.
4. I hit reload on my browser. I now got the page
from gaggle5, but the session ID is different.
Is there a way to see when the session is replicated from
one server to another? I dont see anything in the replication
log, so I dont believe the actual sessions are being replicated.
Thanks,
Neil
--
Neil Aggarwal
JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development Websites, Ecommerce, Java, databases
> -----Original Message-----
> From: Filip Hanik [mailto:mail@filip.net]
> Sent: Tuesday, May 13, 2003 12:06 AM
> To: Tomcat Users List; mail@filip.net
> Cc: Jeff Patterson
> Subject: RE: Sessions not replicating
>
>
> > But, when I opened a browser and visited this page:
> > http://gaggle5.gaggle.net/www-test/index.jsp
> > and then went to this page:
> > http://gnwebapp1.gaggle.net/www-test/index.jsp
>
> these two URLs are different, hence your browser will not send the same
> cookie between them.
> You have to use a load balancer (Apache,
> http://balance.sourceforge.net, or
> my java load balancer)
> to be able to switch server without changing the URL
>
> Filip
>
> > -----Original Message-----
> > From: Neil Aggarwal [mailto:neil@JAMMConsulting.com]
> > Sent: Monday, May 12, 2003 4:11 PM
> > To: mail@filip.net
> > Cc: Tomcat-User; Jeff Patterson
> > Subject: Sessions not replicating
> >
> >
> > Filip:
> >
> > I am trying to follow your document at
> > http://cvs.apache.org/~fhanik/index.html
> > to set-up session replication in tomcat 4.
> >
> > I have two machines running apache 2.0.44 and tomcat 4.1.24 using the
> > mod_webapp
> > connector.
> >
> > These two machines are on a private subnet which gets mapped
> > to public IP addresses. They are
> > gnwebapp1.gaggle.net with internal IP 192.168.0.11
> > gaggle5.gaggle.net with internal IP 192.168.0.5
> >
> > On both servers, in the tomcat server.xml in the <Service
> > name="Tomcat-Apache">
> > tag, I added these lines:
> > <Host name="localhost" debug="0" appBase="webapps"
> > unpackWARs="false" autoDeploy="false">
> > <Context path="/www-test" docBase="www-test" debug="0"
> > reloadable="true" crossContext="true">
> > <Logger
> > className="org.apache.catalina.logger.FileLogger"
> > prefix="localhost_reptest_log."
> > suffix=".txt"
> > timestamp="true"/>
> > <Valve
> className="org.apache.catalina.session.ReplicationValve"
> > filter=".*\.gif;.*\.jpg;.*\.jpeg;.*\.js"
> > debug="0"/>
> > <Manager
> > className="org.apache.catalina.session.InMemoryReplicationManager"
> > debug="10"
> > printToScreen="true"
> > saveOnRestart="false"
> > maxActiveSessions="-1"
> > minIdleSwap="-1"
> > maxIdleSwap="-1"
> > maxIdleBackup="-1"
> > pathname="null"
> > printSessionInfo="true"
> > checkInterval="10"
> > expireSessionsOnShutdown="false"
> >
> > serviceclass="org.apache.catalina.cluster.mcast.McastService"
> > mcastAddr="228.1.2.3"
> > mcastPort="45566"
> > mcastFrequency="500"
> > mcastDropTime="5000"
> > tcpListenAddress="auto"
> > tcpListenPort="4001"
> > tcpSelectorTimeout="100"
> > tcpThreadCount="2"
> > useDirtyFlag="true">
> > </Manager>
> > </Context>
> > </Host>
> >
> > I then started the tomcat and apache on gaggle5 and saw this output in
> > the localhost_reptest log:
> > 2003-05-12 15:57:55 ContextConfig[/www-test]: Missing
> application web.xml,
> > using defaults only
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Starting
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Force random number initialization starting
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Seeding random number generator class java.security.SecureRandom
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Seeding of random number generator has been completed
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Getting message digest component for algorithm MD5
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Completed getting message digest component
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Force random number initialization completed
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Member channel started inside tomcat, version v0.998
> > 2003-05-12 15:57:55 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Sleeping for 5 secs to establish cluster membership
> > 2003-05-12 15:58:00 StandardWrapper[/www-test:default]: Loading
> container
> > servlet default
> > 2003-05-12 15:58:00 StandardWrapper[/www-test:invoker]: Loading
> container
> > servlet invoker
> >
> > So, it seems that the replication manager loaded OK.
> >
> > Then, I started the apache and tomcat on gnwebapp1. In is
> reptest log, I
> > saw this output:
> >
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Starting
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Force random number initialization starting
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Seeding random number generator class java.security.SecureRandom
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Seeding of random number generator has been completed
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Getting message digest component for algorithm MD5
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Completed getting message digest component
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Force random number initialization completed
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Member channel started inside tomcat, version v0.998
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Sleeping for 5 secs to establish cluster membership
> > 2003-05-12 15:59:00 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Replication member
> > added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.
> > 0.5:4001,1
> > 92.168.0.5,4001]
> > 2003-05-12 15:59:05 StandardContext[/www-test]: Posting standard context
> > attributes
> > 2003-05-12 15:59:05 StandardContext[/www-test]: Configuring application
> > event listeners
> > 2003-05-12 15:59:05 StandardContext[/www-test]: Sending
> application start
> > events
> > 2003-05-12 15:59:05 StandardContext[/www-test]: Starting filters
> > 2003-05-12 15:59:05 StandardWrapper[/www-test:default]: Loading
> container
> > servlet default
> > 2003-05-12 15:59:05 StandardWrapper[/www-test:invoker]: Loading
> container
> > servlet invoker
> > 2003-05-12 15:59:05 StandardContext[/www-test]: Starting completed
> >
> > And in the log on the gaggle5 server, I saw this information:
> >
> > 2003-05-12 15:58:59 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Replication member
> > added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.
> > 0.11:4001,
> > 192.168.0.11,4001]
> > 2003-05-12 15:59:04 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > InMemoryReplicationManager.messageDataReceived(): received message
> > 2003-05-12 15:59:04 StandardManager[/www-test]:
> > [InMemoryReplicationManager]
> > Received SessionMessage of type=SESSION-GET-ALL
> >
> > So, it seems that the two machines are talking to each other.
> >
>
> >
> > I got two different session IDs. Also, there were no additional
> > messages in
> > the replication logs.
> >
> > Does session replication work on servers that have apache and
> tomcat using
> > the mod_webapp connector?
> >
> > Thanks,
> > Neil.
> >
> > --
> > Neil Aggarwal
> > JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
> > Custom Internet Development Websites, Ecommerce, Java, databases
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Sessions not replicating
Posted by Filip Hanik <ma...@filip.net>.
> But, when I opened a browser and visited this page:
> http://gaggle5.gaggle.net/www-test/index.jsp
> and then went to this page:
> http://gnwebapp1.gaggle.net/www-test/index.jsp
these two URLs are different, hence your browser will not send the same
cookie between them.
You have to use a load balancer (Apache, http://balance.sourceforge.net, or
my java load balancer)
to be able to switch server without changing the URL
Filip
> -----Original Message-----
> From: Neil Aggarwal [mailto:neil@JAMMConsulting.com]
> Sent: Monday, May 12, 2003 4:11 PM
> To: mail@filip.net
> Cc: Tomcat-User; Jeff Patterson
> Subject: Sessions not replicating
>
>
> Filip:
>
> I am trying to follow your document at
> http://cvs.apache.org/~fhanik/index.html
> to set-up session replication in tomcat 4.
>
> I have two machines running apache 2.0.44 and tomcat 4.1.24 using the
> mod_webapp
> connector.
>
> These two machines are on a private subnet which gets mapped
> to public IP addresses. They are
> gnwebapp1.gaggle.net with internal IP 192.168.0.11
> gaggle5.gaggle.net with internal IP 192.168.0.5
>
> On both servers, in the tomcat server.xml in the <Service
> name="Tomcat-Apache">
> tag, I added these lines:
> <Host name="localhost" debug="0" appBase="webapps"
> unpackWARs="false" autoDeploy="false">
> <Context path="/www-test" docBase="www-test" debug="0"
> reloadable="true" crossContext="true">
> <Logger
> className="org.apache.catalina.logger.FileLogger"
> prefix="localhost_reptest_log."
> suffix=".txt"
> timestamp="true"/>
> <Valve className="org.apache.catalina.session.ReplicationValve"
> filter=".*\.gif;.*\.jpg;.*\.jpeg;.*\.js"
> debug="0"/>
> <Manager
> className="org.apache.catalina.session.InMemoryReplicationManager"
> debug="10"
> printToScreen="true"
> saveOnRestart="false"
> maxActiveSessions="-1"
> minIdleSwap="-1"
> maxIdleSwap="-1"
> maxIdleBackup="-1"
> pathname="null"
> printSessionInfo="true"
> checkInterval="10"
> expireSessionsOnShutdown="false"
>
> serviceclass="org.apache.catalina.cluster.mcast.McastService"
> mcastAddr="228.1.2.3"
> mcastPort="45566"
> mcastFrequency="500"
> mcastDropTime="5000"
> tcpListenAddress="auto"
> tcpListenPort="4001"
> tcpSelectorTimeout="100"
> tcpThreadCount="2"
> useDirtyFlag="true">
> </Manager>
> </Context>
> </Host>
>
> I then started the tomcat and apache on gaggle5 and saw this output in
> the localhost_reptest log:
> 2003-05-12 15:57:55 ContextConfig[/www-test]: Missing application web.xml,
> using defaults only
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Starting
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Force random number initialization starting
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Seeding random number generator class java.security.SecureRandom
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Seeding of random number generator has been completed
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Getting message digest component for algorithm MD5
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Completed getting message digest component
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Force random number initialization completed
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Member channel started inside tomcat, version v0.998
> 2003-05-12 15:57:55 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Sleeping for 5 secs to establish cluster membership
> 2003-05-12 15:58:00 StandardWrapper[/www-test:default]: Loading container
> servlet default
> 2003-05-12 15:58:00 StandardWrapper[/www-test:invoker]: Loading container
> servlet invoker
>
> So, it seems that the replication manager loaded OK.
>
> Then, I started the apache and tomcat on gnwebapp1. In is reptest log, I
> saw this output:
>
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Starting
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Force random number initialization starting
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Seeding random number generator class java.security.SecureRandom
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Seeding of random number generator has been completed
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Getting message digest component for algorithm MD5
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Completed getting message digest component
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Force random number initialization completed
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Member channel started inside tomcat, version v0.998
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Sleeping for 5 secs to establish cluster membership
> 2003-05-12 15:59:00 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Replication member
> added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.
> 0.5:4001,1
> 92.168.0.5,4001]
> 2003-05-12 15:59:05 StandardContext[/www-test]: Posting standard context
> attributes
> 2003-05-12 15:59:05 StandardContext[/www-test]: Configuring application
> event listeners
> 2003-05-12 15:59:05 StandardContext[/www-test]: Sending application start
> events
> 2003-05-12 15:59:05 StandardContext[/www-test]: Starting filters
> 2003-05-12 15:59:05 StandardWrapper[/www-test:default]: Loading container
> servlet default
> 2003-05-12 15:59:05 StandardWrapper[/www-test:invoker]: Loading container
> servlet invoker
> 2003-05-12 15:59:05 StandardContext[/www-test]: Starting completed
>
> And in the log on the gaggle5 server, I saw this information:
>
> 2003-05-12 15:58:59 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Replication member
> added:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.
> 0.11:4001,
> 192.168.0.11,4001]
> 2003-05-12 15:59:04 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> InMemoryReplicationManager.messageDataReceived(): received message
> 2003-05-12 15:59:04 StandardManager[/www-test]:
> [InMemoryReplicationManager]
> Received SessionMessage of type=SESSION-GET-ALL
>
> So, it seems that the two machines are talking to each other.
>
>
> I got two different session IDs. Also, there were no additional
> messages in
> the replication logs.
>
> Does session replication work on servers that have apache and tomcat using
> the mod_webapp connector?
>
> Thanks,
> Neil.
>
> --
> Neil Aggarwal
> JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
> Custom Internet Development Websites, Ecommerce, Java, databases
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org