archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Membership object
    on The default value is 228 0 0 4 Make sure your network is enabled for multicast traffic The multicast address in conjunction with the port is what creates a cluster group To divide up your farm into several different group or to split up QA from production change the port or the address Previously known as mcastAddr port The multicast port the default value is 45564 The multicast port in conjunction with the address is what creates a cluster group To divide up your farm into several different group or to split up QA from production change the port or the address frequency The frequency in milliseconds in which heartbeats are sent out The default value is 500 ms In most cases the default value is sufficient Changing this value simply changes the interval in between heartbeats dropTime The membership component will time out members and notify the Channel if a member fails to send a heartbeat within a give time The default value is 3000 ms This means that if a heartbeat is not received from a member in that timeframe the membership component will notify the cluster of this On a high latency network you may wish to increase this value to protect against false positives Apache Tribes also provides a TcpFailureDetector that will verify a timeout using a TCP connection when a heartbeat timeout has occurred This protects against false positives bind Use this attribute if you wish to bind your multicast traffic to a specific network interface By default or when this attribute is unset it tries to bind to 0 0 0 0 and sometimes on multihomed hosts this becomes a problem ttl The time to live setting for the multicast heartbeats This setting should be a value between 0 and 255 The default

    Original URL path: http://ticket.eppa.es/docs/config/cluster-membership.html (2015-09-25)
    Open archived version from archive


  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Sender object
    the receiver one is non blocking based and the other is built using blocking IO org apache catalina tribes transport bio PooledMultiSender is the blocking implementation and org apache catalina tribes transport nio PooledParallelSender Parallel delivery is not available for the blocking implementation due to the fact that it is blocking a thread on sending data Attributes Common Sender Attributes Attribute Description className Required only available implementation is org apache catalina tribes transport ReplicationTransmitter Common Transport Attributes Attribute Description className Required an implementation of the org apache catalina tribes transport MultiPointSender Non blocking implementation is org apache catalina tribes transport nio PooledParallelSender Blocking implementation is org apache catalina tribes transport bio PooledMultiSender rxBufSize The receive buffer size on the socket Default value is 25188 bytes txBufSize The send buffer size on the socket Default value is 43800 bytes udpRxBufSize The receive buffer size on the datagram socket Default value is 25188 bytes udpTxBufSize The send buffer size on the datagram socket Default value is 43800 bytes directBuffer Possible values are true or false Set to true if you want the receiver to use direct bytebuffers when writing data to the sockets Default value is false keepAliveCount The number of requests that can go through the socket before the socket is closed and reopened for the next request The default value is 1 which is unlimited keepAliveTime The number of milliseconds a connection is kept open after its been opened The default value is 1 which is unlimited timeout Sets the SO TIMEOUT option on the socket The value is in milliseconds and the default value is 3000 milliseconds 3 seconds This timeout starts when a message send attempt is starting until the transfer has been completed For the NIO sockets this will mean that the caller can guarantee that we

    Original URL path: http://ticket.eppa.es/docs/config/cluster-sender.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Receiver object
    network interface to listen for incoming traffic Same as the bind address The default value is auto and translates to java net InetAddress getLocalHost getHostAddress direct Possible values are true or false Set to true if you want the receiver to use direct bytebuffers when reading data from the sockets port The listen port for incoming data The default value is 4000 To avoid port conflicts the receiver will automatically bind to a free port within the range of port bindPort port autoBind So for example if port is 4000 and autoBind is set to 10 then the receiver will open up a server socket on the first available port in the range 4000 4100 autoBind Default value is 100 Use this value if you wish to automatically avoid port conflicts the cluster receiver will try to open a server socket on the port attribute port and then work up autoBind number of times securePort The secure listen port This port is SSL enabled If this attribute is omitted no SSL port is opened up There default value is unset meaning there is no SSL socket available udpPort The UDP listen port If this attribute is omitted no UDP port is opened up There default value is unset meaning there is no UDP listener available selectorTimeout The value in milliseconds for the polling timeout in the NioReceiver On older versions of the JDK there have been bugs that should all now be cleared out where the selector never woke up The default value is a very high 5000 milliseconds maxThreads The maximum number of threads in the receiver thread pool The default value is 6 Adjust this value relative to the number of nodes in the cluster the number of messages being exchanged and the hardware you are running on

    Original URL path: http://ticket.eppa.es/docs/config/cluster-receiver.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Channel Interceptor object
    tribes group interceptors StaticMembershipInterceptor Member className org apache catalina tribes membership StaticMember port 5678 securePort 1 host tomcat01 mydomain com domain staging cluster uniqueId 0 1 2 3 4 5 6 7 8 9 Interceptor Attributes Common Attributes Attribute Description className Required as there is no default optionFlag If you want the interceptor to trigger on certain message depending on the message s option flag you can setup the interceptors flag here The default value is 0 meaning this interceptor will trigger on all messages org apache catalina tribes group interceptors DomainFilterInterceptor Attributes Attribute Description domain The logical cluster domain that this Interceptor accepts Two different type of values are possible 1 Regular string values like staging domain or tomcat cluster will be converted into bytes using ISO 8859 1 encoding 2 byte array in string form for example 216 123 12 3 org apache catalina tribes group interceptors MessageDispatch15Interceptor Attributes Attribute Description className Required This dispatcher uses JDK 1 5 java util concurrent package optionFlag The default and hard coded value is 8 org apache catalina tribes Channel SEND OPTIONS ASYNCHRONOUS The dispatcher will trigger on this value only as it is predefined by Tribes The other attributes are inherited from its base class org apache catalina tribes group interceptors MessageDispatchInterceptor org apache catalina tribes group interceptors MessageDispatchInterceptor Attributes Attribute Description className Required Same implementation as MessageDispatch15Interceptor but with JDK 1 4 compliance optionFlag The default and hard coded value is 8 org apache catalina tribes Channel SEND OPTIONS ASYNCHRONOUS The dispatcher will trigger on this value only as it is predefined by Tribes alwaysSend What behavior should be executed when the dispatch queue is full If true default then the message is is sent synchronously if false an error is thrown maxQueueSize Size in bytes of the dispatch

    Original URL path: http://ticket.eppa.es/docs/config/cluster-interceptor.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Valve object
    This is a simple interface that extends the org apache catalina Valve interface org apache catalina ha tcp ReplicationValve The ReplicationValve will notify the cluster at the end of a HTTP request so that the cluster can make a decision whether there is data to be replicated or not Attributes Attribute Description className Set value to org apache catalina ha tcp ReplicationValve filter For known file extensions or urls you can use this Valve to notify the cluster that the session has not been modified during this request and the cluster doesn t have to probe the session managers for changes If the request matches this filter pattern the cluster assumes there has been no session change An example filter would look like filter gif js jpeg jpg png htm html css txt The filter is a regular expression using java util regex primaryIndicator Boolean value so to true and the replication valve will insert a request attribute with the name defined by the primaryIndicatorName attribute The value inserted into the request attribute is either Boolean TRUE or Boolean FALSE primaryIndicatorName Default value is org apache catalina ha tcp isPrimarySession The value defined here is the name of the request

    Original URL path: http://ticket.eppa.es/docs/config/cluster-valve.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Deployer object
    AJP Containers Context Engine Host Cluster Nested Components Filter Global Resources JarScanner Listeners Loader Manager Realm Resources Valve Cluster Elements Cluster Manager Channel Channel Membership Channel Sender Channel Receiver Channel Interceptor Valve Deployer ClusterListener Global Settings System properties The Cluster

    Original URL path: http://ticket.eppa.es/docs/config/cluster-deployer.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The ClusterListener object
    Table of Contents Introduction org apache catalina ha session ClusterSessionListener org apache catalina ha session JvmRouteSessionIDBinderListener Attributes Common Attributes Introduction The org apache catalina ha ClusterListener base class lets you listen in on messages that are received by the Cluster component org apache catalina ha session ClusterSessionListener When using the DeltaManager the messages are received by the Cluster object and are propagated to the to the manager through this listener

    Original URL path: http://ticket.eppa.es/docs/config/cluster-listener.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - System Properties
    If this is true the default values will be changed for org apache catalina core ApplicationContext GET RESOURCE REQUIRE SLASH org apache catalina core ApplicationDispatcher WRAP SAME OBJECT org apache catalina core StandardHostValve ACCESS SESSION org apache catalina session StandardSession ACTIVITY CHECK org apache catalina session StandardSession LAST ACCESS AT START org apache tomcat util http ServerCookie ALWAYS ADD EXPIRES org apache tomcat util http ServerCookie FWD SLASH IS SEPARATOR org apache tomcat util http ServerCookie STRICT NAMING The resourceOnlyServlets attribute of any Context element The tldNamespaceAware attribute of any Context element The tldValidation attribute of any Context element The xmlNamespaceAware attribute of any Context element The xmlValidation attribute of any Context element Note that changing a number of the above defaults is likely to break the majority of systems as some browsers are unable to correctly handle the cookie headers that result from a strict adherence to the specifications Defaults regardless of whether or not they have been changed by setting org apache catalina STRICT SERVLET COMPLIANCE can always be overridden by explicitly setting the appropriate system property or element attribute org apache catalina connector Response ENFORCE ENCODING IN GET WRITER If this is true then a call to Response getWriter if no character encoding has been specified will result in subsequent calls to Response getCharacterEncoding returning ISO 8859 1 and the Content Type response header will include a charset ISO 8859 1 component SRV 15 2 22 1 If not specified the default specification compliant value of true will be used org apache catalina core ApplicationContext GET RESOURCE REQUIRE SLASH If this is true then the path passed to ServletContext getResource or ServletContext getResourceAsStream must start with If false code like getResource myfolder myresource txt will work If org apache catalina STRICT SERVLET COMPLIANCE is set to true the default of this setting will be true else the default value will be false org apache catalina core ApplicationDispatcher WRAP SAME OBJECT If this is true then any wrapped request or response object passed to an application dispatcher will be checked to ensure that it has wrapped the original request or response If org apache catalina STRICT SERVLET COMPLIANCE is set to true the default of this setting will be true else the default value will be false org apache tomcat util http ServerCookie ALLOW EQUALS IN VALUE If this is true Tomcat will allow characters when parsing unquoted cookie values If false cookie values containing will be terminated when the is encountered and the remainder of the cookie value will be dropped If not specified the default value specification compliant value of false will be used org apache tomcat util http ServerCookie ALLOW HTTP SEPARATORS IN V0 If this is true Tomcat will allow HTTP separators in cookie names and values If not specified the default specification compliant value of false will be used org apache tomcat util http ServerCookie ALWAYS ADD EXPIRES If this is true Tomcat will always add an expires parameter to a SetCookie header

    Original URL path: http://ticket.eppa.es/docs/config/systemprops.html (2015-09-25)
    Open archived version from archive