archive-cr.com » CR » L » LLOBET.CO.CR

Total: 247

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

Or switch to "Titles and links view".
  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Channel object
    or the BackupManager that uses a different replication strategy The ReplicatedContext object does also use the channel object to communicate context attribute changes Nested Components Channel Membership The Membership component is responsible for auto discovering new nodes in the cluster and also to provide for notifications for any nodes that have not responded with a heartbeat The default implementation uses multicast In the membership component you configure how your nodes aka members are to be discovered and or divided up You can always find out more about Apache Tribes Channel Sender The Sender component manages all outbound connections and data messages that are sent over the network from one node to another This component allows messages to be sent in parallel The default implementation uses TCP client sockets and socket tuning for outgoing messages are configured here You can always find out more about Apache Tribes Channel Sender Transport The Transport component is the bottom IO layer for the sender component The default implementation uses non blocking TCP client sockets You can always find out more about Apache Tribes Channel Receiver The receiver component listens for messages from other nodes Here you will configure the cluster thread pool as it will dispatch incoming messages to a thread pool for faster processing The default implementation uses non blocking TCP server sockets You can always find out more about Apache Tribes Channel Interceptor The channel will send messages through an interceptor stack Because of this you have the ability to customize the way messages are sent and received and even how membership is handled You can always find out more about Apache Tribes Attributes Common Attributes Attribute Description className The default value here is org apache catalina tribes group GroupChannel and is currently the only implementation available org apache catalina tribes group

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-channel.html (2015-10-31)
    Open archived version from archive


  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Membership object
    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 value is VM implementation specific domain Apache Tribes has the ability to logically group members into domains by using this domain attribute The org apache catalina tribes Member

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-membership.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Sender object
    time Currently there is no interrupt pause or priority mechanism available but check back soon Nested Elements The nested element Transport is is not required by encouraged as this is where you would set all the socket options for the outgoing messages Please see its attributes below There are two implementations in a similar manner to 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 will not attempt sending the message longer than this timeout value For the blocking IO implementation this translated directly to the soTimeout A timeout will not spawn a retry attempt in order to guarantee the return of the application thread maxRetryAttempts How many times do we retry a failed message that received a IOException at the socket level The default value is 1 meaning we will retry a message that has failed once In other words we will attempt a message send no more than twice One is the original send and one is the maxRetryAttempts ooBInline Boolean value for the socket OOBINLINE option Possible values are true or false soKeepAlive Boolean value for the socket SO KEEPALIVE option Possible values are true or false soLingerOn Boolean value to determine whether to use the SO LINGER socket option Possible values are true or false

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-sender.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Receiver object
    is to use 1 thread per node in the cluster for small clusters and then depending on your message frequency and your hardware you ll find an optimal number of threads peak out at a certain number Attributes Common Attributes Attribute Description className The implementation of the receiver component Two implementations available org apache catalina tribes transport nio NioReceiver and org apache catalina tribes transport bio BioReceiver The org apache catalina tribes transport nio NioReceiver is the preferred implementation address The address 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 4009 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 A higher value doesn t mean more efficiency tune this value according to your own test results minThreads Minimum number of threads to be created when the receiver is started up Default value is 6 ooBInline Boolean value for the socket OOBINLINE option Possible values are true or false rxBufSize The receiver buffer size on the receiving sockets Value is in bytes the default value is 43800 bytes txBufSize The sending buffer size on the receiving sockets Value is in bytes the default value is 25188 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 soKeepAlive Boolean value

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-receiver.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Channel Interceptor object
    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 maxThreads The maximum number of threads in this pool default is 10 maxSpareThreads The number of threads to keep in the pool default is 2 keepAliveTime Maximum number of milliseconds of until Idle thread terminates Default value is 5000 5 seconds 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 queue the default value is 1024 1024 64 64MB sets the maximum queue size for the dispatch queue if the queue fills up one can trigger the behavior if alwaysSend is set to true the message will be sent synchronously if the flag is false an error is thrown org apache catalina tribes group interceptors TcpFailureDetector Attributes Attribute Description connectTimeout Specifies the timeout in milliseconds to use when attempting a TCP connection to the suspect node Default is 1000 performSendTest If true is set send a test message to the suspect node Default is true performReadTest If true is set read the response of the test message that sent Default is false Note if performSendTest is false this attribute will have no effect readTestTimeout Specifies the timeout in milliseconds to use when performing a read test to the suspicious node Default is 5000 removeSuspectsTimeout The maximum time in seconds for remove from removeSuspects Member of removeSuspects will be automatically removed after removeSuspectsTimeout If a negative value specified the removeSuspects members never be removed until disappeared really If the attribute is not provided a default of 300 seconds 5 minutes is used org apache catalina tribes group interceptors TcpPingInterceptor Attributes Attribute Description

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-interceptor.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Valve object
    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 attribute that contains the boolean value if the session is primary on this server or not statistics Boolean value Set to true if you want the valve to collect request statistics Default value is false org apache catalina ha session JvmRouteBinderValve In case of a mod jk failover the JvmRouteBinderValve will replace the jvmWorker attribute in the session Id to make future requests stick to this node If you want failback capability don t enable this valve but if you want your failover to stick and for mod jk not to have to keep probing the node that went down you use this valve Attributes Attribute Description className org apache catalina ha session JvmRouteBinderValve enabled Default value is true Runtime attribute to turn on and off turn over of the session s jvmRoute value sessionIdAttribute Old sessionid before failover is registered in request attributes with this attribute Default attribute name is org apache catalina ha session JvmRouteOrignalSessionID org apache catalina ha authenticator ClusterSingleSignOn The ClusterSingleSignOn supports feature of single sign on in cluster By using ClusterSingleSignOn the security identity authenticated by one web application is recognized by other web applications on the same virtual host and it is propagated to other nodes in the cluster See the Single Sign On special feature on the Host element for more information Note ClusterSingleSignOn can be configured at host level cluster only Attributes Attribute Description className Java class name of the implementation to use This MUST be set to org apache catalina ha authenticator ClusterSingleSignOn cookieDomain Sets the host

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-valve.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The Cluster Deployer object
    the cluster Note FarmWarDeployer can be configured at host level cluster only org apache catalina ha deploy FarmWarDeployer Attributes Attribute Description className The cluster deployer class currently only one is available org apache catalina ha deploy FarmWarDeployer deployDir Deployment directory This is the pathname of a directory where deploy the web applications You may specify an absolute pathname or a pathname that is relative to the CATALINA BASE directory In the current implementation this attribute must be the same value as the Host s appBase tempDir The temporaryDirectory to store binary data when downloading a war from the cluster You may specify an absolute pathname or a pathname that is relative to the CATALINA BASE directory watchDir This is the pathname of a directory where watch for changes add modify remove of web applications You may specify an absolute pathname or a pathname that is relative to the CATALINA BASE directory Note if watchEnabled is false this attribute will have no effect watchEnabled Set to true if you want to watch for changes of web applications Only when this attribute set to true you can trigger a deploy undeploy of web applications The flag s value defaults to false processDeployFrequency Frequency of the Farm watchDir check Cluster wide deployment will be done once for the specified amount of backgrondProcess calls ie the lower the amount the most often the checks will occur The minimum value is 1 and the default value is 2 Note if watchEnabled is false this attribute will have no effect maxValidTime The maximum valid time in seconds of FileMessageFactory FileMessageFactory will be removed immediately after receiving the complete WAR file but when failing to receive a FileMessage which was sent dividing FileMessageFactory will leak without being removed FileMessageFactory that is leaking will be automatically removed after

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-deployer.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Configuration Reference (8.0.24) - The ClusterListener object
    of Contents Introduction org apache catalina ha session ClusterSessionListener 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 Attributes Common Attributes Attribute Description className Comments

    Original URL path: http://www.llobet.co.cr/docs/config/cluster-listener.html (2015-10-31)
    Open archived version from archive



  •