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 (7.0.22) - Building Tomcat
    Ant release resides in its own directory conventionally named apache ant 1 8 x For the remainder of this guide the symbolic name ant home is used to refer to the full pathname of the Ant installation directory directory IMPORTANT Create an ANT HOME environment variable to point the directory ant home and modify the PATH environment variable to include directory ant home bin in its list This makes the ant command line script available which will be used to actually perform the build Checkout or obtain the source code for Tomcat 7 0 Tomcat SVN repository URL http svn apache org repos asf tomcat trunk Tomcat source packages http tomcat apache org download 70 cgi Checkout the source using SVN or download and unpack a source package For the remainder of this guide the symbolic name tomcat source is used to refer to the location where the source has been placed Building Tomcat Use the following commands to build Tomcat cd tomcat source ant NOTE Users accessing the Internet through a proxy must use a properties file to indicate to Ant the proxy configuration Read below for details WARNING Running this command will download binary binaries to the usr share java directory by default Make sure this is appropriate to do so on your computer On Windows this usually corresponds to the C usr share java directory unless Cygwin is used Read below to customize the directory used to download the binaries The build can be controlled by creating a tomcat source build properties file and adding the following content to it Proxy setup Uncomment if using a proxy server proxy host proxy domain proxy port 8080 proxy use on Default Base Path for Dependent Packages Replace this path with the directory path where dependencies binaries should be downloaded base path usr share java Once the build has completed successfully a usable Tomcat installation will have been produced in the tomcat source output build directory and can be started and stopped with the usual scripts Building with Eclipse IMPORTANT This is not a supported means of building Tomcat this information is provided without warranty The only supported means of building Tomcat is with the Ant build described above However some developers like to work on Java code with a Java IDE and the following steps have been used by some developers NOTE This will not let you build everything under Eclipse the build process requires use of Ant for the many stages that aren t simple Java compilations However it will allow you to view and edit the Java code get warnings reformat code perform refactorings run Tomcat under the IDE and so on Sample Eclipse project files and launch targets are provided in the res ide support eclipse directory of the source tree The instructions below will automatically copy these into the required locations An Ant target is provided as a convenience to download all binary dependencies and to create the Eclipse project and classpath files in the

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


  • Apache Tomcat 7 (7.0.22) - Tomcat Developers
    Servlet 18 Clustering 19 Load Balancer 20 Connectors 21 Monitoring and Management 22 Logging 23 APR Native 24 Virtual Hosting 25 Advanced IO 26 Additional Components 27 Mavenized 28 Security Considerations 29 Windows Service 30 Windows Authentication 31 Tomcat s JDBC Pool Reference Release Notes Configuration Tomcat Javadocs Servlet Javadocs JSP 2 2 Javadocs EL 2 2 Javadocs JK 1 2 Documentation Apache Tomcat Development Building Changelog Status Developers Architecture Functional Specs Tomcat Developers Active Developers The list indicates the developers main areas of interest Feel free to add to the list The developers email addresses are login apache org Please do not contact developers directly for any support issues please post to the tomcat users mailing list instead or one of the other support resources some organizations and individual consultants also offer for pay Tomcat support as listed on the support and training page on the Tomcat Wiki Bill Barker billbarker Connectors Costin Manolache costin Catalina Connectors Filip Hanik fhanik Clustering Release Manager Jean Frederic Clere jfclere Connectors Jim Jagielski jim Connectors Konstantin Kolinko kkolinko Catalina Mark Thomas markt CGI SSI WebDAV bug fixing Mladen Turk mturk Connectors Peter Rossbach pero Catalina Clustering JMX Rainer Jung rjung Catalina Clustering

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

  • Apache Tomcat 7 Architecture (7.0.22) - Table of Contents
    of the Tomcat documentation attempts to explain the architecture and design of the Tomcat server It includes significant contributions from several tomcat developers Yoav Shapira yoavs apache org Jeanfrancois Arcand jfarcand apache org Filip Hanik fhanik apache org Table of Contents The information presented is divided into the following sections Overview An overview of the Tomcat server architecture with key terms and concepts Server Startup A detailed description with sequence

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

  • Catalina Functional Specifications (7.0.22) - Table of Contents
    of those features and to test writers trying to decide what to test The functional specifications are divided into the following categories in the menu to the left Administrative Apps Overall requirements for supporting an ability to configure and operate a Tomcat installation through tools as well as detailed requirements for the tools themselves Internal Servlets Requirements for Catalina features that are implemented as internal container managed servlets Realm Implementations

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

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Server Component
    Features Introduction A Server element represents the entire Catalina servlet container Therefore it must be the single outermost element in the conf server xml configuration file Its attributes represent the characteristics of the servlet container as a whole Attributes Common Attributes All implementations of Server support the following attributes Attribute Description className Java class name of the implementation to use This class must implement the org apache catalina Server interface If no class name is specified the standard implementation will be used address The TCP IP address on which this server waits for a shutdown command If no address is specified localhost is used port The TCP IP port number on which this server waits for a shutdown command Set to 1 to disable the shutdown port Note Disabling the shutdown port works well when Tomcat is started using Apache Commons Daemon running as a service on Windows or with jsvc on un xes It cannot be used when running Tomcat with the standard shell scripts though as it will prevent shutdown bat sh and catalina bat sh from stopping it gracefully shutdown The command string that must be received via a TCP IP connection to the specified port number

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

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Service Component
    component for processing incoming requests One or more Service elements may be nested inside a Server element Attributes Common Attributes All implementations of Service support the following attributes Attribute Description className Java class name of the implementation to use This class must implement the org apache catalina Service interface If no class name is specified the standard implementation will be used name The display name of this Service which will

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

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Executor (thread pool)
    executor has to implement the org apache catalina Executor interface The executor is a nested element to the Service element And in order for it to be picked up by the connectors the Executor element has to appear prior to the Connector element in server xml Attributes Common Attributes All implementations of Executor support the following attributes Attribute Description className The class of the implementation The implementation has to implement the org apache catalina Executor interface This interface ensures that the object can be referenced through its name attribute and that implements Lifecycle so that it can be started and stopped with the container The default value for the className is org apache catalina core StandardThreadExecutor name The name used to reference this pool in other places in server xml The name is required and must be unique Standard Implementation The default implementation supports the following attributes Attribute Description threadPriority int The thread priority for threads in the executor the default is Thread NORM PRIORITY daemon boolean Whether the threads should be daemon threads or not the default is true namePrefix String The name prefix for each thread created by the executor The thread name for an individual thread will

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

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The HTTP Connector
    defaults to 2048 connectionLinger The number of seconds during which the sockets used by this Connector will linger when they are closed If not specified the JVM default will be used connectionTimeout The number of milliseconds this Connector will wait after accepting a connection for the request URI line to be presented Use a value of 1 to indicate no i e infinite timeout The default value is 60000 i e 60 seconds but note that the standard server xml that ships with Tomcat sets this to 20000 i e 20 seconds connectionUploadTimeout Specifies the timeout in milliseconds to use while a data upload is in progress This only takes effect if disableUploadTimeout is set to false disableUploadTimeout This flag allows the servlet container to use a different usually longer connection timeout during data upload If not specified this attribute is set to true which disables this longer timeout executor A reference to the name in an Executor element If this attribute is set and the named executor exists the connector will use the executor and all the other thread attributes will be ignored Note that if a shared executor is not specified for a connector then the connector will use a private internal executor to provide the thread pool keepAliveTimeout The number of milliseconds this Connector will wait for another HTTP request before closing the connection The default value is to use the value that has been set for the connectionTimeout attribute Use a value of 1 to indicate no i e infinite timeout maxConnections The maximum number of connections that the server will accept and process at any given time When this number has been reached the server will not accept any more connections until the number of connections falls below this value The operating system may still accept connections based on the acceptCount setting Default value varies by connector type For BIO the default is the value of maxThreads For NIO the default is 10000 For APR native the default is 8192 Note that for APR native on Windows the configured value will be reduced to the highest multiple of 1024 that is less than or equal to maxConnections This is done for performance reasons maxHttpHeaderSize The maximum size of the request and response HTTP header specified in bytes If not specified this attribute is set to 8192 8 KB maxKeepAliveRequests The maximum number of HTTP requests which can be pipelined until the connection is closed by the server Setting this attribute to 1 will disable HTTP 1 0 keep alive as well as HTTP 1 1 keep alive and pipelining Setting this to 1 will allow an unlimited amount of pipelined or keep alive HTTP requests If not specified this attribute is set to 100 maxThreads The maximum number of request processing threads to be created by this Connector which therefore determines the maximum number of simultaneous requests that can be handled If not specified this attribute is set to 200 If an executor is associated with this connector this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool maxTrailerSize Limits the total length of trailing headers in the last chunk of a chunked HTTP request If the value is 1 no limit will be imposed If not specified the default value of 8192 will be used minSpareThreads The minimum number of threads always kept running If not specified the default of 10 is used noCompressionUserAgents The value is a regular expression using java util regex matching the user agent header of HTTP clients for which compression should not be used because these clients although they do advertise support for the feature have a broken implementation The default value is an empty String regexp matching disabled processorCache The protocol handler caches Processor objects to speed up performance This setting dictates how many of these objects get cached 1 means unlimited default is 200 If not using Servlet 3 0 asynchronous processing a good default is to use the same as the maxThreads setting If using Servlet 3 0 asynchronous processing a good default is to use the larger of maxThreads and the maximum number of expected concurrent requests synchronous and asynchronous restrictedUserAgents The value is a regular expression using java util regex matching matching the user agent header of HTTP clients for which HTTP 1 1 or HTTP 1 0 keep alive should not be used even if the clients advertise support for these features The default value is an empty String regexp matching disabled server Overrides the Server header for the http response If set the value for this attribute overrides the Tomcat default and any Server header set by a web application If not set any value specified by the application is used If the application does not specify a value then Apache Coyote 1 1 is used Unless you are paranoid you won t need this feature socketBuffer The size in bytes of the buffer to be provided for socket output buffering 1 can be specified to disable the use of a buffer By default a buffers of 9000 bytes will be used SSLEnabled Use this attribute to enable SSL traffic on a connector To turn on SSL handshake encryption decryption on a connector set this value to true The default value is false When turning this value true you will want to set the scheme and the secure attributes as well to pass the correct request getScheme and request isSecure values to the servlets See SSL Support for more information tcpNoDelay If set to true the TCP NO DELAY option will be set on the server socket which improves performance under most circumstances This is set to true by default threadPriority The priority of the request processing threads within the JVM The default value is java lang Thread NORM PRIORITY See the JavaDoc for the java lang Thread class for more details on what this priority means Java TCP socket attributes The BIO and NIO implementation support the following Java TCP socket attributes in addition to the common Connector and HTTP attributes listed above Attribute Description socket rxBufSize int The socket receive buffer SO RCVBUF size in bytes JVM default used if not set socket txBufSize int The socket send buffer SO SNDBUF size in bytes JVM default used if not set socket tcpNoDelay bool This is equivalent to standard attribute tcpNoDelay socket soKeepAlive bool Boolean value for the socket s keep alive setting SO KEEPALIVE JVM default used if not set socket ooBInline bool Boolean value for the socket OOBINLINE setting JVM default used if not set socket soReuseAddress bool Boolean value for the sockets reuse address option SO REUSEADDR JVM default used if not set socket soLingerOn bool Boolean value for the sockets so linger option SO LINGER A value for the standard attribute connectionLinger that is 0 is equivalent to setting this to true A value for the standard attribute connectionLinger that is 0 is equivalent to setting this to false Both this attribute and soLingerTime must be set else the JVM defaults will be used for both socket soLingerTime int Value in seconds for the sockets so linger option SO LINGER This is equivalent to standard attribute connectionLinger Both this attribute and soLingerOn must be set else the JVM defaults will be used for both socket soTimeout This is equivalent to standard attribute connectionTimeout socket soTrafficClass byte Value between 0 and 255 for the traffic class on the socket JVM default used if not set Note On some JDK versions setting soTrafficClass causes a problem A work around for this is to add the Djava net preferIPv4Stack true value to your JVM options socket performanceConnectionTime int The first value for the performance settings See Socket Performance Options All three performance attributes must be set else the JVM defaults will be used for all three socket performanceLatency int The second value for the performance settings See Socket Performance Options All three performance attributes must be set else the JVM defaults will be used for all three socket performanceBandwidth int The third value for the performance settings See Socket Performance Options All three performance attributes must be set else the JVM defaults will be used for all three socket unlockTimeout int The timeout for a socket unlock When a connector is stopped it will try to release the acceptor thread by opening a connector to itself The default value is 250 and the value is in milliseconds BIO specific configuration The following attributes are specific to the BIO connector Attribute Description disableKeepAlivePercentage The percentage of processing threads that have to be in use before HTTP keep alives are disabled to improve scalability Values less than 0 will be changed to 0 and values greater than 100 will be changed to 100 If not specified the default value is 75 NIO specific configuration The following attributes are specific to the NIO connector Attribute Description acceptorThreadPriority int The priority of the acceptor threads The threads used to accept new connections The default value is java lang Thread NORM PRIORITY See the JavaDoc for the java lang Thread class for more details on what this priority means pollerThreadCount int The number of threads to be used to run for the polling events Default value is 1 per processor Can t see a reason to go above that But experiment and find your own results pollerThreadPriority int The priority of the poller threads The default value is java lang Thread NORM PRIORITY See the JavaDoc for the java lang Thread class for more details on what this priority means selectorTimeout int The time in milliseconds to timeout on a select for the poller This value is important since connection clean up is done on the same thread so do not set this value to an extremely high one The default value is 1000 milliseconds useComet bool Whether to allow comet servlets or not Default value is true useSendfile bool Use this attribute to enable or disable sendfile capability The default value is true socket directBuffer bool Boolean value whether to use direct ByteBuffers or java mapped ByteBuffers Default is false When you are using direct buffers make sure you allocate the appropriate amount of memory for the direct memory space On Sun s JDK that would be something like XX MaxDirectMemorySize 256m socket appReadBufSize int Each connection that is opened up in Tomcat get associated with a read ByteBuffer This attribute controls the size of this buffer By default this read buffer is sized at 8192 bytes For lower concurrency you can increase this to buffer more data For an extreme amount of keep alive connections decrease this number or increase your heap size socket appWriteBufSize int Each connection that is opened up in Tomcat get associated with a write ByteBuffer This attribute controls the size of this buffer By default this write buffer is sized at 8192 bytes For low concurrency you can increase this to buffer more response data For an extreme amount of keep alive connections decrease this number or increase your heap size The default value here is pretty low you should up it if you are not dealing with tens of thousands concurrent connections socket bufferPool int The NIO connector uses a class called NioChannel that holds elements linked to a socket To reduce garbage collection the NIO connector caches these channel objects This value specifies the size of this cache The default value is 500 and represents that the cache will hold 500 NioChannel objects Other values are 1 for unlimited cache and 0 for no cache socket bufferPoolSize int The NioChannel pool can also be size based not used object based The size is calculated as follows NioChannel buffer size read buffer size write buffer size SecureNioChannel buffer size application read buffer size application write buffer size network read buffer size network write buffer size The value is in bytes the default value is 1024 1024 100 100MB socket processorCache int Tomcat will cache SocketProcessor objects to reduce garbage collection The integer value specifies how many objects to keep in the cache at most The default is 500 Other values are 1 for unlimited cache and 0 for no cache socket keyCache int Tomcat will cache KeyAttachment objects to reduce garbage collection The integer value specifies how many objects to keep in the cache at most The default is 500 Other values are 1 for unlimited cache and 0 for no cache socket eventCache int Tomcat will cache PollerEvent objects to reduce garbage collection The integer value specifies how many objects to keep in the cache at most The default is 500 Other values are 1 for unlimited cache and 0 for no cache selectorPool maxSelectors int The max selectors to be used in the pool to reduce selector contention Use this option when the command line org apache tomcat util net NioSelectorShared value is set to false Default value is 200 selectorPool maxSpareSelectors int The max spare selectors to be used in the pool to reduce selector contention When a selector is returned to the pool the system can decide to keep it or let it be GC d Use this option when the command line org apache tomcat util net NioSelectorShared value is set to false Default value is 1 unlimited command line options The following command line options are available for the NIO connector Dorg apache tomcat util net NioSelectorShared true false default is true Set this value to false if you wish to use a selector for each thread When you set it to false you can control the size of the pool of selectors by using the selectorPool maxSelectors attribute oomParachute int The NIO connector implements an OutOfMemoryError strategy called parachute It holds a chunk of data as a byte array In case of an OOM this chunk of data is released and the error is reported This will give the VM enough room to clean up The oomParachute represents the size in bytes of the parachute the byte array The default value is 1024 1024 1MB Please note this only works for OOM errors regarding the Java Heap space and there is absolutely no guarantee that you will be able to recover at all If you have an OOM outside of the Java Heap then this parachute trick will not help APR native specific configuration The following attributes are specific to the APR native connector Attribute Description deferAccept Sets the TCP DEFER ACCEPT flag on the listening socket for this connector The default value is true where TCP DEFER ACCEPT is supported by the operating system otherwise it is false pollerSize Amount of sockets that the poller responsible for polling kept alive connections can hold at a given time Extra connections will be closed right away The default value is 8192 corresponding to 8192 keep alive connections This is a synonym for maxConnections pollerThreadCount Number of threads used to poll kept alive connections On Windows the default is chosen so that the sockets managed by each thread is less than 1024 For Linux the default is 1 Changing the default on Windows is likely to have a negative performance impact pollTime Duration of a poll call in microseconds Lowering this value will slightly decrease latency of connections being kept alive in some cases but will use more CPU as more poll calls are being made The default value is 2000 2ms sendfileSize Amount of sockets that the poller responsible for sending static files asynchronously can hold at a given time Extra connections will be closed right away without any data being sent resulting in a zero length file on the client side Note that in most cases sendfile is a call that will return right away being taken care of synchronously by the kernel and the sendfile poller will not be used so the amount of static files which can be sent concurrently is much larger than the specified amount The default value is 1024 sendfileThreadCount Number of threads used service sendfile sockets On Windows the default is chosen so that the sockets managed by each thread is less than 1024 For Linux the default is 1 Changing the default on Windows is likely to have a negative performance impact threadPriority int The priority of the acceptor and poller threads The default value is java lang Thread NORM PRIORITY See the JavaDoc for the java lang Thread class for more details on what this priority means useComet bool Whether to allow comet servlets or not Default value is true useSendfile bool Use this attribute to enable or disable sendfile capability The default value is true Nested Components None at this time Special Features HTTP 1 1 and HTTP 1 0 Support This Connector supports all of the required features of the HTTP 1 1 protocol as described in RFC 2616 including persistent connections pipelining expectations and chunked encoding If the client typically a browser supports only HTTP 1 0 the Connector will gracefully fall back to supporting this protocol as well No special configuration is required to enable this support The Connector also supports HTTP 1 0 keep alive RFC 2616 requires that HTTP servers always begin their responses with the highest HTTP version that they claim to support Therefore this Connector will always return HTTP 1 1 at the beginning of its responses Proxy Support The proxyName and proxyPort attributes can be used when Tomcat is run behind a proxy server These attributes modify the values returned to web applications that call the request getServerName and request getServerPort methods which are often used to construct absolute URLs for redirects Without configuring these attributes the values returned would reflect the server name and port on which the connection from the proxy server was received rather than the server name and port to whom the client directed the original request For more information see the Proxy Support HOW TO SSL Support You can

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