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 Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Developers
    22 Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Developers Developers

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



  • the MVC architecture used in this application It is generally mapped to the do filename extension with a servlet mapping element and all form submits in the app will be submitted to a request URI like saveCustomer do which will therefore be mapped to this servlet The initialization parameter names for this servlet are the servlet path that will be received by this servlet after the filename extension is removed

    Original URL path: http://ticket.eppa.es/docs/appdev/web.xml.txt (2015-09-25)
    Open archived version from archive



  • (No additional info available in detailed archive for this subpage)
    Original URL path: /docs/appdev/build.xml.txt (2015-09-25)



  • so that a container can listen to multiple connectors ie single entry org apache coyote tomcat5 CoyoteConnector Connectors to listen for incoming requests only It also adds the following rulesets to the digester NamingRuleSet EngineRuleSet HostRuleSet ContextRuleSet b4 Load the server xml and parse it using the digester Parsing the server xml using the digester is an automatic XML object mapping tool that will create the objects defined in server xml Startup of the actual container has not started yet b5 Assigns System out and System err to the SystemLogHandler class b6 Calls initialize on all components this makes each object register itself with the JMX agent During the process call the Connectors also initialize the adapters The adapters are the components that do the request pre processing Typical adapters are HTTP1 1 default if no protocol is specified org apache coyote http11 Http11Protocol AJP1 3 for mod jk etc c Catalina start c1 Starts the NamingContext and binds all JNDI references into it c2 Starts the services under which are StandardService starts Engine ContainerBase Logger Loader Realm Cluster etc c3 StandardHost started by the service Configures a ErrorReportValvem to do proper HTML output for different HTTP errors codes Starts the Valves in the pipeline at least the ErrorReportValve Configures the StandardHostValve this valves ties the Webapp Class loader to the thread context it also finds the session for the request and invokes the context pipeline Starts the HostConfig component This component deploys all the webapps webapps conf Catalina localhost xml Webapps are installed using the deployer StandardHostDeployer The deployer will create a Digester for your context this digester will then invoke ContextConfig start The ContextConfig start will process the default web xml conf web xml and then process the applications web xml WEB INF web xml c4 During the lifetime of the container StandardEngine there is a background thread that keeps checking if the context has changed If a context changes timestamp of war file context xml file web xml then a reload is issued stop remove deploy start d Tomcat receives a request on an HTTP port d1 The request is received by a separate thread which is waiting in the PoolTcpEndPoint class It is waiting for a request in a regular ServerSocket accept method When a request is received this thread wakes up d2 The PoolTcpEndPoint assigns the a TcpConnection to handle the request It also supplies a JMX object name to the catalina container not used I believe d3 The processor to handle the request in this case is Coyote Http11Processor and the process method is invoked This same processor is also continuing to check the input stream of the socket until the keep alive point is reached or the connection is disconnected d4 The HTTP request is parsed using an internal buffer class Coyote Http11 Internal Buffer The buffer class parses the request line the headers etc and store the result in a Coyote request not an HTTP request This request contains all the HTTP

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



  •