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 processed in 332 ms
Dec 22, 2009 2:17:07 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 22, 2009 2:17:07 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Dec 22, 2009 2:17:07 PM org.apache.catalina.ha.tcp.SimpleTcpCluster start
INFO: Cluster is about to start
Dec 22, 2009 2:17:07 PM org.apache.catalina.tribes.transport.ReceiverBase bind
INFO: Receiver Server Socket bound to:/10.5.1.102:4000
Dec 22, 2009 2:17:07 PM org.apache.catalina.tribes.membership.McastServiceImpl setupSocket
INFO: Attempting to bind the multicast socket to /224.0.0.0:45564
Dec 22, 2009 2:17:07 PM org.apache.catalina.tribes.membership.McastServiceImpl setupSocket
INFO: Setting multihome multicast interface to:/10.5.1.102
Dec 22, 2009 2:17:07 PM org.apache.catalina.ha.tcp.SimpleTcpCluster start
SEVERE: Unable to start cluster.
org.apache.catalina.tribes.ChannelException: java.net.SocketException: An operation was attempted on something that is not a socket; No faulty members identified.
...
Caused by: java.net.SocketException: An operation was attempted on something that is not a socket

On Dec 26, 2009, at 1:34 AM, Konstantin Kolinko wrote:

2) John Tangney,
do you see the following one or two INFO messages in Tomcat log:
log.info("Attempting to bind the multicast socket to "+address +":"+port); log.info("Binding to multicast address, failed. Binding to port only.");

INFO: Attempting to bind the multicast socket to /224.0.0.0:45564

3)
It is possible to create unbound MulticastSocket, by passing a null
instead of  SocketAddress to its constructor.

Maybe the  socket.setInterface(mcastBindAddress);  call will succeed
if we create an unbound socket with "new MulticastSocket(null)", make
setInterface() call, and call bind() later.

When I get back to work I will be able to follow up on your research and perhaps try #3 – unless someone else tries it first. If that works, we'll either need to run a custom Tomcat or wait for the patch (assuming it's accepted) is released.

Thanks again for your help!
---johnt


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to