Thanx. To end this original thread, yes, that's the answer. When you take the Reciever-Part in Clustering... <Receiver className="org.apache.catalina.cluster.tcp.ReplicationListener" tcpListenAddress="auto" tcpListenPort="4001" tcpSelectorTimeout="100" tcpThreadCount="6"/>
...just give the next instance on the same machine a higher portnumber: tcpListenPort="4002", et viola, running as smooth as tomcat normally does... -- Björn Andersen www.premiere.de -----Ursprüngliche Nachricht----- Von: Filip Hanik (lists) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 18. August 2004 15:37 An: Tomcat Users List Betreff: RE: Tomcat Clusterin Multicast Multiinstances no, the address already in use is tcpListenPort, that has to change if you run two instances on the same machine Filip -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 18, 2004 2:51 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: AW: Tomcat Clusterin Multicast Multiinstances Hi again, you are right with the 2Gb, sorry. It's leaving a netto of 1.6 GB ish for Tomcat here. My problem was referring to the clustersection of server.xml rather than the standard IP: mcastAddr = the multicast address, has to be the same for all the nodes mcastPort = the multicast port, has to be the same for all the nodes So even when everything else can be configured per Instance, these addr needs to be the same. So when I start up the second instance of Tomcat on the server, it says that the mcastAddr (="228.0.0.4" port 45564) is already in use and it can't bind to it ... ------------------ INFO: Sleeping for 2000 secs to establish cluster membership 18.08.2004 09:47:19 org.apache.catalina.cluster.tcp.ReplicationListener run SCHWERWIEGEND: Unable to start cluster listener. java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind(Native Method) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at org.apache.catalina.cluster.tcp.ReplicationListener.listen(ReplicationListen er.java:104) at org.apache.catalina.cluster.tcp.ReplicationListener.run(ReplicationListener. java:85) at java.lang.Thread.run(Unknown Source) ----------------- -- Björn Andersen www.premiere.de -----Ursprüngliche Nachricht----- Von: Dale, Matt [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 17. August 2004 18:19 An: Tomcat Users List Betreff: RE: Tomcat Clusterin Multicast Multiinstances Memory limit should be 2 Gig for JVM's running in a 32 bit operating system. More for the 64 bit JVM's. I think you would have to have virtual IP addresses on that machine and run tomcats on specific IP addresses for you to use the multicasting. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 13:42 To: [EMAIL PROTECTED] Subject: Tomcat Clusterin Multicast Multiinstances Hi, can anyone tell me how Tomcats can be configured as a cluster with session replication when there is more than one TC-Instance on one machine? We need multi-instance because of the 1 Gig mem-limit to the jvm's. Or has that changed meanwhile too? -- Björn Andersen Webservices www.premiere.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]