Konstantin,
Thanks for your in-depth analysis! I am still on vacation so I have
had not had a chance to follow all your references.
Here is some log output:
INFO: Initializing Coyote HTTP/1.1 on http-8180
Dec 22, 2009 2:17:07 PM org.apache.catalina.startup.Catalina load
INFO: Initialization p
2009/12/26 John Tangney :
> We are still experiencing this problem.
>
> To summarize:
> 1) We are using 6.0.18.
> 2) A single Tomcat works fine and joins the cluster.
> 3) Two Tomcats on the SAME MACHINE (different ports - duh) but multicasting
> to DIFFERENT multicast IPs each join their respectiv
We are still experiencing this problem.
To summarize:
1) We are using 6.0.18.
2) A single Tomcat works fine and joins the cluster.
3) Two Tomcats on the SAME MACHINE (different ports - duh) but
multicasting to DIFFERENT multicast IPs each join their respective
clusters. (yes, two clusters.)
4
On Dec 23, 2009, at 2:36 PM, Filip Hanik - Dev Lists wrote:
On 12/23/2009 01:46 PM, John Tangney wrote:
On Dec 23, 2009, at 12:19 PM, Filip Hanik - Dev Lists wrote:
On 12/23/2009 11:42 AM, John Tangney wrote:
it's failing on this operation:
socket.setInterface(mcastBindAddress);
There is a
On 12/23/2009 01:46 PM, John Tangney wrote:
On Dec 23, 2009, at 12:19 PM, Filip Hanik - Dev Lists wrote:
On 12/23/2009 11:42 AM, John Tangney wrote:
it's failing on this operation:
socket.setInterface(mcastBindAddress);
There is a small chance that Window's doesn't allow multicast
sockets t
On Dec 23, 2009, at 12:19 PM, Filip Hanik - Dev Lists wrote:
On 12/23/2009 11:42 AM, John Tangney wrote:
it's failing on this operation:
socket.setInterface(mcastBindAddress);
There is a small chance that Window's doesn't allow multicast
sockets to be bound to an IP
try removing the "bind"
On 12/23/2009 11:42 AM, John Tangney wrote:
Thanks for your response, Filip!
On Dec 23, 2009, at 6:05 AM, Filip Hanik - Dev Lists wrote:
sorry, ignore previous post,
Yeah, I had the same reaction to 224.0.0.0 but it works when one
Tomcat is running, so I assumed it's OK.
it's failing on
Thanks for your response, Filip!
On Dec 23, 2009, at 6:05 AM, Filip Hanik - Dev Lists wrote:
sorry, ignore previous post,
Yeah, I had the same reaction to 224.0.0.0 but it works when one
Tomcat is running, so I assumed it's OK.
it's failing on this operation:
socket.setInterface(mcastBi
sorry, ignore previous post, it's failing on this operation:
socket.setInterface(mcastBindAddress);
There is a small chance that Window's doesn't allow multicast sockets to
be bound to an IP
try removing the "bind" attribute
Filip
On 12/23/2009 06:48 AM, Filip Hanik - Dev Lists wrote:
addr
address="224.0.0.0"
that's not an IP, the last 0 is not allowed, must be 1-254
Filip
On 12/22/2009 05:36 PM, John Tangney wrote:
We run two tomcats on the same Windows Server 2008 box. They have their
server.xml tweaked so that they use unique ports. Here's a diff:
$ diff server.xml /cygdrive
On 23/12/2009 00:36, John Tangney wrote:
We run two tomcats on the same Windows Server 2008 box. They have their
server.xml tweaked so that they use unique ports. Here's a diff:
$ diff server.xml /cygdrive/c/Program\ Files/Apache\ Software\
Foundation/Tomcat\ 6.0/conf/server.xml
22c22
<
---
--johnt
--
View this message in context:
http://old.nabble.com/Error-running-two-tomcats-in-same-cluster-on-same-Windows-box-tp26896489p26896489.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubs
12 matches
Mail list logo
