Sorry, I thought the question was obvious. It deploys but then undeploys
with the severe error I mentioned below. I don't want the error I
want the FarmWarDeployer to deploy the war to both Tomcats and
remain deployed...
C:/Tomcats/apache-tomcat-7.0.12_node1
C:/Tomcats/apache-tomcat-
On 29/04/2011 15:29, Seth Lenzi wrote:
>
> I'm trying to use org.apache.catalina.ha.deploy.FarmWarDeployer with
> Tomcat 7.0.12 to deploy my war files to a Tomcat cluster (two Tomcat's
> both version 7.0.12.)
>
> They war file is successfully deployed to both Tomcats but then the war
> is immedia
I'm trying to use org.apache.catalina.ha.deploy.FarmWarDeployer with
Tomcat 7.0.12 to deploy my war files to a Tomcat cluster (two Tomcat's
both version 7.0.12.)
They war file is successfully deployed to both Tomcats but then the war
is immediately un-deployed from one of them.
The followi
FYI - running one of the instances in a VMWare virtual machine works fine.
Mitch
Mitch Claborn wrote:
> Yes to both questions. What a bummer. I'll try running the second
> instance on a VM an see what happens.
>
> Mitch
>
>
> Filip Hanik - Dev Lists wrote:
>
>> Wait a second, are both your i
Yes to both questions. What a bummer. I'll try running the second
instance on a VM an see what happens.
Mitch
Filip Hanik - Dev Lists wrote:
> Wait a second, are both your instances on the same machine? Are you
> running Apache Tomcat 6.0.20
> there was a serious regression, with the loopback
Wait a second, are both your instances on the same machine? Are you
running Apache Tomcat 6.0.20
there was a serious regression, with the loopback turned off.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47308
Filip
On 07/17/2009 08:54 AM, Mitch Claborn wrote:
ping 224.0.0.1
PING 224.0.
ping 224.0.0.1
PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data.
64 bytes from 192.168.3.254: icmp_seq=1 ttl=255 time=0.895 ms
64 bytes from 192.168.3.254: icmp_seq=2 ttl=255 time=0.693 ms
64 bytes from 192.168.3.254: icmp_seq=3 ttl=255 time=0.686 ms
Mitch
Filip Hanik - Dev Lists wrote:
>
> corr
correct, you're members are not discovering each other.
and its purely multicast related.
what do you get when you do
ping 224.0.0.1
Filip
On 07/16/2009 05:16 PM, Mitch Claborn wrote:
Not having much luck getting a simple cluster to work. Using nginx as
a front end/load balancer against tw
Not having much luck getting a simple cluster to work. Using nginx as
a front end/load balancer against two tomcat instances on the same
machine (for now). SuSE Linux 11.1. I see this message in the startup
log, making me think the tomcat instances are not talking:
INFO: Manager [localhost#/St
