Re: Tomcat in a clustered Enviroment
WHY AM I STIL GETTING YOUR MESSAGES TO EACH OTHER? PLEASE REMOVE ME FROMTHE MAILING LIST I WISH TO UNSUBSCRIBE TO YOUR SITE.PLEASE ANSWER ME -Original Message- From: Peter Rossbach [EMAIL PROTECTED] Sent: Apr 25, 2005 12:55 AM To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: Tomcat in a clustered Enviroment Your are sure that the ip interface is configured for Multicast? Peter Josef Whiter schrieb: I tried using the Cluster directive with the Membership directive in there but it still wont bind to the virtual interface. Josef On Fri, 22 Apr 2005, Josef Whiter wrote: Hello, Its IBM's 1.4.2 jvm, Red Hat Enterprise Linux 3 and tomcat 5.0.28. I will look into that directive. Thank you, Josef Whiter On Fri, 22 Apr 2005, Peter Rossbach wrote: Hello, which tomcat, os, jvm you used? On windows without network cable the cluster need an explizit binding Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastBindAddress=127.0.0.1 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Peter Josef Whiter schrieb: Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - 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] - 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] - 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]
Re: Tomcat in a clustered Enviroment
I tried using the Cluster directive with the Membership directive in there but it still wont bind to the virtual interface. Josef On Fri, 22 Apr 2005, Josef Whiter wrote: Hello, Its IBM's 1.4.2 jvm, Red Hat Enterprise Linux 3 and tomcat 5.0.28. I will look into that directive. Thank you, Josef Whiter On Fri, 22 Apr 2005, Peter Rossbach wrote: Hello, which tomcat, os, jvm you used? On windows without network cable the cluster need an explizit binding Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastBindAddress=127.0.0.1 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Peter Josef Whiter schrieb: Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - 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] - 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]
Re: Tomcat in a clustered Enviroment
Your are sure that the ip interface is configured for Multicast? Peter Josef Whiter schrieb: I tried using the Cluster directive with the Membership directive in there but it still wont bind to the virtual interface. Josef On Fri, 22 Apr 2005, Josef Whiter wrote: Hello, Its IBM's 1.4.2 jvm, Red Hat Enterprise Linux 3 and tomcat 5.0.28. I will look into that directive. Thank you, Josef Whiter On Fri, 22 Apr 2005, Peter Rossbach wrote: Hello, which tomcat, os, jvm you used? On windows without network cable the cluster need an explizit binding Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastBindAddress=127.0.0.1 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Peter Josef Whiter schrieb: Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat in a clustered Enviroment
Hello, which tomcat, os, jvm you used? On windows without network cable the cluster need an explizit binding Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastBindAddress=127.0.0.1 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Peter Josef Whiter schrieb: Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - 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]
Re: Tomcat in a clustered Enviroment
Hello, Its IBM's 1.4.2 jvm, Red Hat Enterprise Linux 3 and tomcat 5.0.28. I will look into that directive. Thank you, Josef Whiter On Fri, 22 Apr 2005, Peter Rossbach wrote: Hello, which tomcat, os, jvm you used? On windows without network cable the cluster need an explizit binding Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastBindAddress=127.0.0.1 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000/ Peter Josef Whiter schrieb: Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat in a clustered Enviroment
Hello, Does tomcat just not bind to virtual interfaces, or other IP addresses in general? If anybody has any suggestions on this issue it would be very helpful, since i cant seem to get this cluster up and running. Thank you, Josef Whiter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat in a clustered Enviroment
Hello, I am trying to setup tomcat in a simple failover cluster. I have configured tomcat to bind to the virtual IP address thats setup in cluster suite, but whenever I start the service it does not open any of the ports its supposed to. I get one little blip in my catalina.out file, which never shows up when i start it normally Created MBeanServer with ID: 42d8b7dd:1034f377a4e:-8000:legion3.perf.redhat.com:1 The process shows up in ps auxw like normal, it just wont accept any connections, not to the Virtual IP, not to localhost or the actual IP of the cluster node. I've attatched my server.xml file so you can see my configuration. Any help would be greatly appreciated. Thank you, Josef Whiter !-- Example Server Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Comment these entries out to disable JMX MBeans support -- !-- You may also configure custom components (e.g. Valves/Realms) by including your own mbean-descriptor file(s), and setting the descriptors attribute to point to a ';' seperated list of paths (in the ClassLoader sense) of files to add to the default list. e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ !-- Global JNDI resources -- GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- !-- Note : To use gzip compression you
