The benefits are that you can get it to start and stop with the machine and a non 
tomcat admin can start and stop it using the services. It can also be remotely started 
if you have the right tools. And it doesnt require a user to be logged in for the 
service to remain running.

-----Original Message-----
From: Shakeel [mailto:[EMAIL PROTECTED]
Sent: 01 August 2004 15:03
To: Tomcat Users List
Subject: RE: Tomcat Clusterin Multicast Multiinstances


Can any one quickly tell the comparison of running tomcat as a service or
without a windows service.
I mean what are the benifits of running tomcat as a windows service.

S H A K E E L   A H M A D



-----Original Message-----
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 18, 2004 6:37 PM
To: Tomcat Users List
Subject: 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]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to