WO2003032185A1 - System for application server messaging with multiple dispatch pools - Google Patents
System for application server messaging with multiple dispatch pools Download PDFInfo
- Publication number
- WO2003032185A1 WO2003032185A1 PCT/US2002/031724 US0231724W WO03032185A1 WO 2003032185 A1 WO2003032185 A1 WO 2003032185A1 US 0231724 W US0231724 W US 0231724W WO 03032185 A1 WO03032185 A1 WO 03032185A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- queue
- requests
- resource
- queues
- server
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5011—Pool
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5018—Thread allocation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5021—Priority
Definitions
- An embodiment of the invention relates generally to application and transaction servers and particularly to a system for supporting message queuing and threads with multiple dispatch pools.
- J2EE Java 2 Platform, Enterprise Edition
- Sun Microsystems, Inc. in collaboration with leaders from throughout the enterprise software arena, defines one ofthe current standards for developing multi-tier enterprise applications.
- J2EE provides a component-based approach to the design, development, assembly, and deployment of enterprise applications, which both reduces the cost and enables fasten design and implementation.
- the J2EE platform gives the developer a multi-tiered distributed application model, the ability to reuse components, a unified security model, and flexible transaction control. Not only can they deliver innovative customer solutions to market faster than ever, but the resultant platform-independent J2EE component-based solutions are not tied to the products and application program interfaces (APIs) of any one vendor.
- APIs application program interfaces
- the J2EE specification defines the following kinds of components: application client components; Enterprise JavaBeans (EJB); servlets and Java Server Pages (JSP) (also called Web components); and applets.
- EJB Enterprise JavaBeans
- JSP Java Server Pages
- a multi-tiered distributed application model implies that the application logic is divided into components according to function, and different application components may make up a J2EE application on the same or different servers. Where an application component is actually installed depends on which tier in the multi-tiered J2EE environment the application component belongs. These tiers are depicted in Figure 1.
- an application server tier 104 is used to develop EJB containers and/or presentation containers such as servlets, JSP, and html pages 114. These in turn are used as an interface between a client tier 102, where the clients 108 and client applications are deployed, and a backend tier 106, used for hosting enterprise or legacy applications such Enterprise Resource Planning (ERP) systems.
- ERP Enterprise Resource Planning
- Client tier- can be browsers, Java-based programs, or other Web-enabled programming environments running within the client tier, both inside and outside of corporate firewalls.
- Application Server tier - Normally this tier hosts a combination of presentation logic and business logic to support client requests. Presentation logic is supported via JSP pages and servlets that display HTML pages, while business logic is supported via Remote Method Invocation (RMI) objects and EJBs 112. EJBs rely upon the container environmentfortransactions. lifecycle and state management, resource pooling, security, etc., which together make up the run time environment in which the beans are executed.
- RMI Remote Method Invocation
- EJBs rely upon the container environmentfortransactions. lifecycle and state management, resource pooling, security, etc., which together make up the run time environment in which the beans are executed.
- Back-end tier This is generally a combination of existing applications and data stores.
- EIS Enterprise Information Systems
- ERP Enterprise Resource Planning
- mainframe transaction processing database systems
- legacy information systems other legacy information systems.
- Client and application code can, for example, use the Java Naming and Directory Interface (JNDI) 116 to look up user-defined objects such as enterprise beans, and environment entries such as the location of the Java Database Connector (JDBC) DataSource objects, which in turn are used for looking up resources in backend tier, and message connections.
- JNDI Java Naming and Directory Interface
- JDBC Java Database Connector
- Application behavior such as security and transaction management can be configured at deployment time on Web and enterprise bean components.
- This deployment time feature decouples application logic from the configuration settings that might vary with the assembly.
- the J2EE security model lets a developer configure a Web or enterprise bean component so that system resources are accessed only by authorized users.
- a Web component can be configured to prompt for a user name and password.
- An Enterprise Bean component can be configured so that only persons in specific groups can invoke certain kinds of its methods.
- a servlet component might be configured to have some of its methods accessible to everyone, and a few methods accessible to only certain privileged persons in an organization. The same servlet component can be configured for another environment to have all methods available to everyone, or all methods available to only a select few.
- Some application servers such as the WebLogic Server product from BEA Systems, Inc., San Jose, California, use an Access Control List (ACL) mechanism that allows for fine-grained control of the usage of components running on the server.
- ACL Access Control List
- a developer can define at the Java Method level what can, or cannot, be executed by which user or group of users.
- This ACL mechanism covers anything that runs on the application server except for EJBs, which have their own access control mechanism defined in the EJB specification.
- Security realms allow the administrator to import information from existing authorization or authentication systems into the ACL.
- Java Servlets [0012] A servlet is a program that extends the functionality of a
- a servlet receives a request from a client, dynamically generates the response (possibly querying databases to fulfill the request), and then sends the response containing an HTML or XML document to the client.
- Servlets are similar to CGI but are typically easier to write, since servlets use Java classes and streams. They execute faster because servlets are compiled to Java byte code and at run time the servlet instance is kept in memory, each client request spawning a new thread. Servlets make it easy to generate data to an HTTP response stream in a dynamic fashion. Each client request is performed as a new connection, so flow control does not come naturally between requests. To allow for this session management maintains the state of specific clients between requests. In some application servers, servlets make use of the HTTP session object to save their state between method requests. This object can be replicated in a clustered environment for failover purposes. Java Server Pages
- JSP pages are a text-based, presentation-centric way to develop servlets. JSP pages offer all the benefits of servlets, and when combined with a JavaBeans class, provide an easy way to keep content and display logic separate. Both JSP pages and servlets are more desirable than Common Gateway Interface (CGI), because they are platform-independent, and use less overhead. JSP pages can be used with JavaBeans classes to define Web templates for building a Web site made up of pages with a similar look and feel. The JavaBeans class performs the data rendering, so the templates have no Java code. This means they can be maintained by an HTML editor. Simple Web-based application using a JSP page can be used to bind content to application logic using custom tags or scriptlets instead of a JavaBeans class. Custom tags are bundled into tag libraries that are imported into a JSP page. Scriptlets are small Java code segments embedded directly in the
- JDBC Database Access Services
- JDBC acts as a bridge to relational databases, and is modeled on the ODBC (Open Database Connectivity) specification. It decouples the database from the program code through the use of drivers. Some implementations of JDBC provide support for advanced data types, and also support the functionality of scrollable result sets and batch updates.
- JMS Java Messaging Services
- JMS is the J2EE mechanism used to support the exchange of messages between Java programs. This is how Java supports asynchronous communication, wherein the sender and receiver don't need to be aware of each other and thus can operate independently.
- JMS currently supports two messaging models: [0016] Point to point - which is based on message queues. In this model message producer sends a message to a queue. A message consumer can attach itself to a queue to listen for messages. When a message arrives on the queue, the consumer takes it off the queue and responds to it. Messages can be sent to just one queue and will be used by just one consumer. Consumers have the option to filter messages to specify the exact message types they want. [0017] Publish and subscribe - which allows producers to send messages to a topic and for all the registered consumers for that topic to retrieve those messages. In this case, many consumers can receive the same message.
- CORBA objects to use an Interface Definition Language (IDL) to specify a contract, i.e., how they are going to interact with other objects.
- IDL Interface Definition Language
- contracts may be defined between the Java world and the CORBA world.
- JDK Sun's Java Development Kit
- ORB Object Request Broker
- HOP Internet InterORB
- event queues provide a method for implementing threading policies on that CORBA server. In practice the event queues support the desired threading policy for CORBA requests, and integrate the processing of non-CORBA events within the threading policy.
- a multi-threaded CORBA server such as the Orbix server from lona Software, can for example implement policies which determine how many threads are created, when those threads are created, and which requests are handled by which threads.
- Implementing a particular policy typically involves creating a number of queues and worker threads and programming a logic to determine which queue to use for each incoming event.
- Multi-threaded CORBA servers can thus process several
- Threading policies can be customized for different needs, depending on how the work of handling requests should be shared between them. These options include the following:
- One thread per operation In this scenario a new thread is created to handle each incoming request. This option provides maximum concurrency, but sometimes creates too many threads if the server receives a large number of concurrent requests at peak load.
- Use of a thread pool In this scenario requests are queued and handled by the first available thread in a pool of threads. The maximum number of threads, and hence the server load, is restricted by limiting the size of the pool.
- One thread per object Following this option one or more request queues are maintained for each object. This option provides full concurrency between objects but serializes access to each individual object.
- One thread per client A request queue is maintained for each client. This option ensures equal treatment of clients, by controlling the number of thread resources allocated to each.
- J2EE-based transaction and application servers is the concept or prioritization of requests. Although threading policies can be designed for maximum throughput in terms of request management these are few options in terms of request prioritization. Many current server products use a pool of threads for reading requests from clients from the network. Once a complete request is read into the queue it must be dispatched for execution in the server. But there is little to allow a developer to prioritize the complete requests prior to dispatch. [0025] Prioritization of requests is a commonly desired feature, but is difficult to implement because of concerns about the complexity it adds to the underlying server code and because of new problems, such as priority inversion, which it can create. The addition of multiple queues would provide the software administrator or developer with a priority mechanism that manages these concerns better than a true priority scheme would.
- Throttling of requests is another feature commonly requested by application server customers. This is commonly requested where part of the workload requires a large amount of memory, CPU time, or other resource. The system can not process many of these requests simultaneously.
- Many application servers provide dispatch options that allow a request to execute in the same thread that read the request or to enqueue it on a queue which feeds a pool of worker threads. Using this configuration one can control various quality of service parameters of the requests. For instance requests may be expedited by executing them directly in the thread which read them thus skipping the queue. Alternately some requests may be throttled by assigning them to a queue which is tended by only a limited number of threads.
- an embodiment of the invention provides a system or mechanism for use with an application server, that enhances the servers threading model, i.e. the policy by which threads are assigned to perform work requests.
- Embodiments of the invention can be used with a wide range of application servers, including, for example, the WebLogic Server product from BEA Systems, Inc., San Jose, California.
- An application server, or any server, designed to use an embodiment of the invention employs a threading model which uses multiple thread pools - including an asynchronous pool (sometimes referred to as reader threads) and a synchronous pool (referred to as execute threads). This combination of pools allows the system to prioritize requests. The design also successfully tolerates user code that performs blocking operations.
- the asynchronous thread pool waits on an asynchronous input mechanism (referred to herein as a multiplexor, or muxer) for asynchronous read results to become available.
- a thread from the pool looks at the message and dispatches it by making the appropriate callbacks.
- the dispatch callbacks usually queue the request for later processing by the synchronous thread pool.
- certain non-blocking, priority requests are services directly in the callback. By aggressively accepting input, these high priority requests do not wait to be read while lower priority requests run.
- the synchronous thread pool waits on a queue of requests. Once a request is available a thread from the synchronous pool takes the request from the queue, processes it, and sends out the result. While processing the request, the thread may execute code, such as sending out the result, which causes the thread to block. [0031]
- the addition of asynchronous output and asynchronous responses alleviates some of the need for thread process tuning, which is a common task in traditional systems.
- an embodiment of the invention allows for configuration of multiple synchronous thread pools so as to provide more fine-grained control over the processing of different request types.
- An embodiment of the invention also supports the ability to provide multiple execute queues within a single server. These queues are individually similar to current execute queues. Each execute queue has a pool of worker threads assigned to pulling work from the queue. In accordance with one embodiment of the invention, each server has one default execute queue and either zero, or one or more, custom execute queues. The addition of multiple queues provides several benefits over traditional systems, including support for prioritization, throttling of requests and reduced queue contention. Queues can be independently allocated for high priority and low priority requests. The system administrator can then tune the number of threads assigned to these queues until the required throughput for each class of work is achieved.
- Figure 1 shows an illustration of a J2EE compatible server architecture that can utilize an embodiment of the present invention.
- Figure 2 shows a threading model in accordance with an embodiment of the invention.
- Figure 3 shows an illustration of a multiple dispatch queue system in accordance with an embodiment of the invention.
- Figure 4 shows an illustration of a multiple thread dispatch system in accordance with an embodiment of the invention.
- Figure 5 shows a flowchart of a multiple dispatch process in accordance with an embodiment of the invention.
- an embodiment of the invention provides extensions for a flexible dispatch policy system for use with transaction, application and messaging servers, and particulariyforuse with RMI (Remote Method Invocation), EJB (Enterprise Java Bean) and Servlets.
- An application server transaction server, or messaging server (all commonly hereinafter simply referred to as application server), that incorporates an embodiment of the invention uses a pool of threads for reading requests from clients from the network. Once a complete request is read, it must be dispatched for execution in the server.
- An embodiment of the invention provides the ability to configure this dispatch policy. For servlets this is configured on a per-URL (Uniform Resource Locator) basis. For RMI and EJB the dispatch policy is configured on a per method basis.
- Dispatch options provided by an embodiment of the invention allow the request to be executed in the same thread that read the request, or alternatively to be enqueued on a queue which feeds a pool of worker threads.
- this variable dispatch configuration one can control various quality of service parameters of the requests. For example, requests may be expedited by executing them directly in the thread which read them, thus skipping the queue. Alternately some requests can be throttled by assigning them to a queue which is tended by only a limited number of threads.
- An embodiment of the invention provides new features related to application server messaging but which can be used with any server type that requires messaging of some sort.
- the threading model the policy by which threads are assigned to perform work requests.
- the server employs a threading model which uses two thread pools an asynchronous pool (readerthreads) and a synchronous pool (execute threads). This combination of pools and flexibility in dispatch options allows an administrator to effectively prioritize requests, while tolerating user code that performs blocking operations.
- Figure 2 shows an illustration of a thread pool 206 as provided by an embodiment of the invention that is used to pass requests to a server resource 205.
- the server includes configuration information for each resource that determines the dispatch policy 211 to be used with a particular resource.
- the asynchronous thread pool 208 waits on an asynchronous input mechanism 202 (sometimes referred to as a muxer) for asynchronous read results to become available. Once a result is available, a thread from the pool looks at the message and dispatches it by making the appropriate callbacks. The dispatch callbacks usually queue the request for later processing by a synchronous thread pool. However certain non-blocking, priority requests are serviced directly in the callback. By allowing the asynchronous thread pool to aggressively accepting input, high priority requests 212 do not wait to be read while low priority requests 216 run.
- Embodiments of the invention additionally provide the ability for the asynchronous thread pool to perform network output operations. This particular feature is described in more detail in Provisional Patent Application "SYSTEM FOR APPLICATION SERVER MESSAGING
- the synchronous thread pool 210 waits on a queue of requests 204. Once a request is available, a thread from the pool takes the request from the queue, processes it, and sends out the result 216 to the resource 205. While processing the request the thread may execute code, such as sending out the result, which causes the thread to block.
- the number of threads should therefore be tuned so that there is always one thread per CPU that is in the runnable state. Appropriate tuning of a server is important for performance reasons.
- the addition of asynchronous output and asynchronous responses as used in an embodiment of the invention alleviates some of the need for this tuning.
- An embodiment of the invention also provides an administrator until the ability to configure multiple synchronous thread pools so as to provide more fine-grained control over the processing of different request types.
- Dispatch is the process of taking a server request and passing it to the appropriate place to be serviced.
- the server request may be any signal from the server including for example the result of input read from the network, a time trigger, or the continuation of some other piece of work.
- direct dispatch the thread which generated the incoming message also processes that message. The dispatching thread is not replaced with another thread while it is processing the request so it is important that the work to be performed will not block the dispatching thread for any significant amount of time.
- FIG. 3 shows a traditional execute queue mechanism.
- a request from the client directed to a particular resource is queued on an execute queue 304.
- a set of one or more worker threads 306, 308 or thread processes retrieve the entries 310 from the queue and execute them against the resource, returning the result to the client.
- the problem with this mechanism is that the queue operates on a first in / first out manner, and there is no way to prioritize particular entries so as to process one entry in the queue before another. [0046] In queued dispatch, the dispatching thread puts the incoming message on a queue where it will later be dequeued and serviced by a worker thread.
- Other embodiments can use multiple execute queues.
- the queue length may be bounded or unbounded, although when the queue length is unbounded care must be taken to prevent problems with memory usage. Typically all user requests are dispatched to a queue rather than directed.
- Figure 4 shows how multiple queues provided by an embodiment of the invention are used to build a dispatch policy.
- requests from the client are passed to a queue socket selected from a plurality of queue sockets 402, 404, 406.
- the sockets operate in parallel, allowing entries on one socket to be performed at the same time, or prior to, those in another socket. This separate and parallel operation allows the system to prioritize the requests.
- a set of one or more asynchronous threads 412, 414, 416 are used to service the socket requests and to provide access to the resource. Groups of asynchronous threads (e.g. 412 and 414) can be shared between groups of sockets (e.g. 404 and 406).
- a socket 402 may have a dedicated thread 416, to allow for reliable or high priority servicing of the particular requests within that socket.
- Application servers embodying or incorporating an embodiment of the invention support the ability to have multiple execute queues in a single server.
- each execute queue has a pool of worker threads assigned to pulling work from the queue.
- each server has one default execute queue, and either zero or one or more custom execute queues. The addition of multiple queues provides several benefits, including supportfor prioritization, throttling of requests and reduced queue contention.
- queues can be independently allocated for high priority and low priority requests. The administrator can then tune the number of threads assigned to these queues until the required throughput for each class of work is achieved.
- Throttling of requests is a feature commonly requested by application server users. Throttling is important in those instances where part of the workload requires a large amount of memory, CPU time, or other resource. Typically the system can not process many of these requests simultaneously.
- An embodiment of the invention provides mechanisms for request throttling in that all of these types of requests can be sent to a queue which is configured with the proper amount of threads to ensure that system resources are conserved.
- Queue contention is a problem in benchmarks of heavily loaded systems serving multiple short requests.
- An embodiment of the invention provides a mechanism to successfully tackle this problem by spreading the workload out over several queues, queue contention can be reduced. Requests be distributed across the queues in such a manner as to maximize throughput.
- FIG. 5 shows a flowchart of the multiple queue dispatch policy in accordance with an embodiment of the invention.
- a request to access a particular resource is received by the server. This may be a request to access, for example, a particular service, a URL, or a database.
- a dispatch thread places the request on one of the multiple message queues or sockets.
- the combination of providing a default execute queue, and multiple customer execute queues allows, in step 506, the system or system administrator the ability to prioritize the request, by specifying which socket or queue it should be placed in.
- a worker thread retrieves the request from the appropriate message queue, and, in step 510, the request is processed at the server, and the result returned to the client.
- a typical Remote Method Invocation (RMI) implementation is adapted to take advantage of multiple queues.
- the RMI descriptor is generalized to allow a per-method queuing policy to be set. This functionality provides a mechanism to specify direct or queued dispatch.
- a RequestDispatcher message is dispatched to the RJVM level.
- RJVM then queries its RuntimeDescriptor and determines which dispatch policy should be applied to the request.
- Adapting a servlet implementation to take advantage of multiple queues can be similarly performed.
- the meta data describing the dispatch policy can be placed in the servlet's deployment descriptor. The point at which requests are normally queued is to a point where the servlet to be invoked has been determined. At this point the appropriate dispatch policy can be determined, and appropriate action taken. HTTP tunneling mechanisms can also be modified to use this mechanism.
- timing services may be adapted to take advantage of the multiple queues. Additions to any API may also be made to allow the specification of the dispatch policy for a particular timer. This can be integrated with current direct dispatch mechanisms that services the trigger directly in the timing thread.
- an embodiment of the invention provides a set of commands and syntaxes.
- the following section provides a guide to configuring servlets, jsps, ejbs, and rmi objects to use these pools in accordance with one embodiment of the invention. It will be evident that an embodiment of the invention is not limited to the particular implementations described below which are given for purposes of illustration, but instead can be used with other implementations and with other application servers or servers.
- the developer or administrator can use the servlet init parameters to set the queue name, for example via the tag "wl-dispatch-policy" in systems that use web.xml files for configuration.
- the web.xml file contains an init-param section like the exemplary one shown below:
- JSPs can be registered like servlets.
- the following code example shows a JSP registered to use a queue named "testqueue": ⁇ servlet>
- EJBC and RMIC can be modified to take a dispatch Pol icy flag, for allowing the configuration of dispatch policy or the command line, i.e.:
- Java eblogic .rmic -dispatchPolicy testqueue Java weblogic .ejbc -dispatchPolicy testqueue ...
- Some embodiments of the invention allow for setting the priority of threads within a particular thread pool. In accordance with one embodiment of the invention however no mechanism is provided to allow the configuration to set the priority of the threads in the pool. This is intentional since the semantics of thread scheduling varies between platforms, and the system is less likely to run into starvation/priority inversion problems if all execute threads have the same priority.
- a topic closely related to prioritization is quality of service
- QOS Quality of Service
- a good reason to use a separate execute queue is to avoid deadlock conditions.
- a separate queue can be configured for the additional requests. For example, consider the situation in which a servlet "a" reads from a JMS queue "b". If all of the server's execute threads are executing servlet "a”, then there will be no execute threads left to deliver messages from queue "b", so none of the work can progress. This situation can be avoided by defining a separate queue for servlet "a”.
- Throttling and optimizing throughput Another good reason to use a separate queue is to throttle requests which use some fixed pool of resources. For example, if a particular job uses a lot of memory it may be more optimal to dispatch it to a queue with a limited number of associated threads. In this way the system can limit the maximum number of jobs of this type which are running simultaneously, and minimize any risk of the server running out of memory. [0066] A related use is to separate those requests which require access to a resource from one particular pool, from those requests in another pool which don't require access. For example, consider a case where a server is serving two EJBs.
- EJB 'a' uses a connection pool to access a database, while EJB 'b' performs only some in-memory work (or perhaps uses a different pool.) If the number of threads is greater than the number of connections in the pool, then the system may encounter a situation wherein several threads are blocked trying to get a connection from the pool while processing requests for 'a'. At the same time there may be other requests for 'b' sitting in the queue which could proceed if only there were free execute threads.
- Livelocks and priority inversion While judicious use of separate queues can reduce the chance of deadlocks as explained above, they also introduce a new class of possible problems which can be quite difficult to debug. As a trivial example it is possible that two remote calls made from the same client to the same server, but dispatched to separate queues, will return in a different order than anticipated. [0068]
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002362654A AU2002362654B2 (en) | 2001-10-05 | 2002-10-04 | System for application server messaging with multiple dispatch pools |
JP2003535082A JP4287276B2 (en) | 2001-10-05 | 2002-10-04 | System for application server messaging using multiple shipping pools |
EP02800901.7A EP1438678B1 (en) | 2001-10-05 | 2002-10-04 | System for application server messaging with multiple dispatch pools |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US32754301P | 2001-10-05 | 2001-10-05 | |
US60/327,543 | 2001-10-05 | ||
US10/264,439 | 2002-10-03 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003032185A1 true WO2003032185A1 (en) | 2003-04-17 |
Family
ID=23276980
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2002/031724 WO2003032185A1 (en) | 2001-10-05 | 2002-10-04 | System for application server messaging with multiple dispatch pools |
Country Status (6)
Country | Link |
---|---|
US (2) | US6886041B2 (en) |
EP (1) | EP1438678B1 (en) |
JP (1) | JP4287276B2 (en) |
CN (1) | CN100342369C (en) |
AU (1) | AU2002362654B2 (en) |
WO (1) | WO2003032185A1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1686763A1 (en) * | 2005-02-01 | 2006-08-02 | Microsoft Corporation | Access-limited buffer |
GB2429086A (en) * | 2005-08-10 | 2007-02-14 | Symbian Software Ltd | Improving the efficiency of file server requests in a computing device |
CN100347675C (en) * | 2004-06-29 | 2007-11-07 | 北京大学 | Property optimizing method for applying server |
JP2008533630A (en) * | 2005-03-21 | 2008-08-21 | デクステラ・インコーポレイテッド | Data management for mobile data systems |
GB2507294A (en) * | 2012-10-25 | 2014-04-30 | Ibm | Server work-load management using request prioritization |
CN112612586A (en) * | 2020-12-24 | 2021-04-06 | 大唐互联科技(武汉)有限公司 | Method and system for designing connection equipment based on reactive architecture |
Families Citing this family (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7003570B2 (en) * | 2001-10-05 | 2006-02-21 | Bea Systems, Inc. | System for integrating java servlets with asynchronous messages |
US6886041B2 (en) * | 2001-10-05 | 2005-04-26 | Bea Systems, Inc. | System for application server messaging with multiple dispatch pools |
US7222148B2 (en) * | 2002-05-02 | 2007-05-22 | Bea Systems, Inc. | System and method for providing highly available processing of asynchronous service requests |
US20030233485A1 (en) * | 2002-06-13 | 2003-12-18 | Mircrosoft Corporation | Event queue |
CA2703143A1 (en) * | 2002-12-17 | 2004-07-08 | Breathablebaby, Llc | Crib shield system and other breathable apparatus |
US7039914B2 (en) * | 2003-03-07 | 2006-05-02 | Cisco Technology, Inc. | Message processing in network forwarding engine by tracking order of assigned thread in order group |
JP4041002B2 (en) * | 2003-03-24 | 2008-01-30 | 株式会社三菱東京Ufj銀行 | Database update processing system, update data input method for database update, update data processing method, and program |
US7185060B2 (en) * | 2003-03-26 | 2007-02-27 | Microsoft Corporation | Message processing pipeline for streams |
US7424721B2 (en) * | 2003-05-19 | 2008-09-09 | Sun Microsystems, Inc. | Inter-object communication interface bridge |
US7246359B2 (en) * | 2003-07-31 | 2007-07-17 | International Business Machines Corporation | Methods, systems and computer program products for maintaining association integrity of enterprise JavaBeans (EJB) during EJB passivation and reactivation |
US8041821B2 (en) * | 2003-11-26 | 2011-10-18 | International Business Machines Corporation | Connection pool management |
US7693847B1 (en) * | 2004-07-13 | 2010-04-06 | Teradata Us, Inc. | Administering workload groups |
US8176117B2 (en) * | 2003-12-19 | 2012-05-08 | Stmicroelectronics, Inc. | Accelerator for object-oriented communications and method |
US7444536B1 (en) | 2004-04-16 | 2008-10-28 | Sun Microsystems, Inc. | RMI-IIOP request failover mechanism |
US7448041B2 (en) * | 2004-04-28 | 2008-11-04 | International Business Machines Corporation | Interfacing an application server to remote resources using Enterprise Java Beans as interface components |
US7657892B2 (en) * | 2004-05-20 | 2010-02-02 | Bea Systems, Inc. | System and method for application server with self-tuned threading model |
US7509429B2 (en) * | 2004-05-28 | 2009-03-24 | Sap Ag | Message endpoint activation |
US20050267918A1 (en) * | 2004-05-28 | 2005-12-01 | Gatev Andrei A | System and method for bundling deployment descriptor files within an enterprise archive for fast reliable resource setup at deployment time |
US20050289212A1 (en) * | 2004-06-01 | 2005-12-29 | Tankov Nikolal D | Non-transactional resource reference |
US7594237B2 (en) | 2004-06-01 | 2009-09-22 | Sap Ag | Program object to support connection generation |
US9582313B2 (en) * | 2004-06-03 | 2017-02-28 | Sap Se | Connection resource system |
US7676810B2 (en) * | 2004-06-03 | 2010-03-09 | Sap Ag | Identification of execution context |
US7657658B2 (en) * | 2004-06-07 | 2010-02-02 | Sap Ag | Resource adapter deployment |
US20050289551A1 (en) * | 2004-06-29 | 2005-12-29 | Waldemar Wojtkiewicz | Mechanism for prioritizing context swapping |
US20060026214A1 (en) * | 2004-07-29 | 2006-02-02 | International Business Machines Corporation | Switching from synchronous to asynchronous processing |
US7565662B2 (en) * | 2004-09-24 | 2009-07-21 | International Business Machines Corporation | Program agent initiated processing of enqueued event actions |
US8055821B2 (en) * | 2004-11-17 | 2011-11-08 | International Business Machines Corporation | Apparatus, system, and method for converting a synchronous interface into an asynchronous interface |
US7770150B2 (en) * | 2004-12-15 | 2010-08-03 | International Business Machines Corporation | Apparatus, system, and method for sharing and accessing data by scopes |
WO2006089385A1 (en) * | 2005-02-22 | 2006-08-31 | Nextair Corporation | Wireless communication device use of application server applications |
US8090873B1 (en) * | 2005-03-14 | 2012-01-03 | Oracle America, Inc. | Methods and systems for high throughput information refinement |
US8005791B1 (en) | 2005-03-14 | 2011-08-23 | Oracle America, Inc. | Methods and systems for publishing aggregated data to a business logic tier |
US8055689B1 (en) | 2005-03-14 | 2011-11-08 | Oracle America, Inc. | Methods and systems for distributing information model nodes in memory |
US8005933B2 (en) * | 2005-04-13 | 2011-08-23 | International Business Machines Corporation | Probabalistic throttling of application server requests |
CN100450105C (en) * | 2005-09-13 | 2009-01-07 | 中兴通讯股份有限公司 | Synchronous information interface realizing method based on JAVA information service |
US8671133B2 (en) * | 2005-11-29 | 2014-03-11 | The Boeing Company | System having an energy efficient network infrastructure for communication between distributed processing nodes |
CN100385863C (en) * | 2005-12-29 | 2008-04-30 | 华为技术有限公司 | Media resource distributing method |
US9092278B2 (en) | 2006-07-07 | 2015-07-28 | International Business Machines Corporation | Determining the processing order of a plurality of events |
US20080148275A1 (en) * | 2006-10-30 | 2008-06-19 | Alexander Krits | Efficient Order-Preserving Delivery of Concurrent Messages |
EP2095276B1 (en) * | 2006-12-19 | 2016-11-30 | International Business Machines Corporation | Method and system for reducing difference in the time of retrieval of data retrieved from different sources |
US9112808B2 (en) | 2007-02-06 | 2015-08-18 | At&T Intellectual Property Ii, L.P. | Devices, systems, and methods for providing data |
US20080209435A1 (en) * | 2007-02-23 | 2008-08-28 | Microsoft Corporation | Scalable workflow management system |
US7711822B1 (en) * | 2007-03-26 | 2010-05-04 | Oracle America, Inc. | Resource management in application servers |
US20080270974A1 (en) * | 2007-04-30 | 2008-10-30 | Krasimir Topchiyski | Enterprise JavaBeans Metadata Model |
US8326816B2 (en) | 2010-05-06 | 2012-12-04 | Oracle International Corporation | Fine grain synchronization for database replay |
US8438144B2 (en) * | 2010-08-27 | 2013-05-07 | Oracle International Corporation | Transactionally consistent database replay in an environment with connection pooling |
US8611378B2 (en) * | 2007-05-29 | 2013-12-17 | Red Hat, Inc. | Message handling multiplexer |
US7733863B2 (en) * | 2007-05-30 | 2010-06-08 | Red Hat, Inc. | Out of band messages |
US7992153B2 (en) * | 2007-05-30 | 2011-08-02 | Red Hat, Inc. | Queuing for thread pools using number of bytes |
US7921227B2 (en) * | 2007-05-30 | 2011-04-05 | Red Hat, Inc. | Concurrent stack |
US8505028B2 (en) * | 2007-05-30 | 2013-08-06 | Red Hat, Inc. | Flow control protocol |
US7793140B2 (en) * | 2007-10-15 | 2010-09-07 | International Business Machines Corporation | Method and system for handling failover in a distributed environment that uses session affinity |
US8719841B2 (en) * | 2007-11-16 | 2014-05-06 | Microsoft Corporation | Dispatch mechanism for coordinating application and communication medium state |
US8505030B2 (en) * | 2007-11-16 | 2013-08-06 | Microsoft Corporation | Coordinating resources using a volatile network intermediary |
US9021503B2 (en) * | 2007-11-16 | 2015-04-28 | Microsoft Technology Licensing, Llc | Coordinating application state and communication medium state |
CN101262352B (en) * | 2008-03-04 | 2010-10-13 | 浙江大学 | Uniform data accelerated processing method in integrated secure management |
US8205202B1 (en) * | 2008-04-03 | 2012-06-19 | Sprint Communications Company L.P. | Management of processing threads |
US10474477B2 (en) | 2008-10-10 | 2019-11-12 | Adobe Inc. | Collaborative and non-collaborative workspace application container with application persistence |
US20100241760A1 (en) * | 2009-03-18 | 2010-09-23 | Microsoft Corporation | Web Front-End Throttling |
US20100250651A1 (en) * | 2009-03-31 | 2010-09-30 | Inventec Corporation | Data access method for making asynchronous request to block device |
US8301706B2 (en) | 2009-06-15 | 2012-10-30 | Microsoft Corporation | Routing of pooled messages via an intermediary |
US9292702B2 (en) * | 2009-08-20 | 2016-03-22 | International Business Machines Corporation | Dynamic switching of security configurations |
US8230478B2 (en) * | 2009-08-27 | 2012-07-24 | International Business Machines Corporation | Flexibly assigning security configurations to applications |
US8296411B2 (en) * | 2010-03-01 | 2012-10-23 | International Business Machines Corporation | Programmatically determining an execution mode for a request dispatch utilizing historic metrics |
US8549538B2 (en) * | 2010-03-18 | 2013-10-01 | Microsoft Corporation | Coordinating communication medium state for subtasks |
US8250234B2 (en) | 2010-04-26 | 2012-08-21 | Microsoft Corporation | Hierarchically disassembling messages |
US9886315B2 (en) * | 2010-08-27 | 2018-02-06 | Ebay Inc. | Identity and semaphore-based quality of service |
US8856460B2 (en) | 2010-09-15 | 2014-10-07 | Oracle International Corporation | System and method for zero buffer copying in a middleware environment |
US9727396B2 (en) * | 2010-11-30 | 2017-08-08 | Red Hat, Inc. | Message queue deployment |
US20120151479A1 (en) * | 2010-12-10 | 2012-06-14 | Salesforce.Com, Inc. | Horizontal splitting of tasks within a homogenous pool of virtual machines |
US9086909B2 (en) * | 2011-05-17 | 2015-07-21 | Oracle International Corporation | System and method for supporting work sharing muxing in a cluster |
US9110715B2 (en) * | 2013-02-28 | 2015-08-18 | Oracle International Corporation | System and method for using a sequencer in a concurrent priority queue |
CN103164273A (en) * | 2012-09-06 | 2013-06-19 | 佳都新太科技股份有限公司 | Method for changing synchronous service call to asynchronous parallel call with self-expanding choking algorithm |
CN103197968B (en) * | 2013-03-18 | 2016-03-30 | 焦点科技股份有限公司 | A kind of thread pool disposal route and system merging synchronous asynchronous feature |
CN104063279B (en) * | 2013-03-20 | 2018-12-28 | 腾讯科技(深圳)有限公司 | Method for scheduling task, device and terminal |
US10346148B2 (en) | 2013-08-12 | 2019-07-09 | Amazon Technologies, Inc. | Per request computer system instances |
US9280372B2 (en) | 2013-08-12 | 2016-03-08 | Amazon Technologies, Inc. | Request processing techniques |
US9348634B2 (en) | 2013-08-12 | 2016-05-24 | Amazon Technologies, Inc. | Fast-booting application image using variation points in application source code |
US9705755B1 (en) * | 2013-08-14 | 2017-07-11 | Amazon Technologies, Inc. | Application definition deployment with request filters employing base groups |
WO2015179509A1 (en) * | 2014-05-21 | 2015-11-26 | Georgia State University Research Foundation, Inc. | High-performance computing framework for cloud computing environments |
CN104598563B (en) * | 2015-01-08 | 2018-09-04 | 北京京东尚科信息技术有限公司 | High concurrent date storage method and device |
CN104793071A (en) * | 2015-03-28 | 2015-07-22 | 合肥天海电气技术有限公司 | Power grid fault diagnosis system based on J2EE distributed type technology |
WO2017066966A1 (en) * | 2015-10-22 | 2017-04-27 | Oracle International Corporation | System and method for providing mssq notifications in transactional processing environment |
US10261902B2 (en) | 2016-01-04 | 2019-04-16 | Toshiba Memory Corporation | Parallel processing of a series of data units for writing |
US10635497B2 (en) * | 2017-05-05 | 2020-04-28 | Cavium, Llc | Method and apparatus for job pre-scheduling by distributed job manager in a digital multi-processor system |
US10616346B2 (en) * | 2017-07-28 | 2020-04-07 | International Business Machines Corporation | Server connection capacity management |
CN109117260B (en) * | 2018-08-30 | 2021-01-01 | 百度在线网络技术(北京)有限公司 | Task scheduling method, device, equipment and medium |
US11553047B2 (en) | 2018-11-30 | 2023-01-10 | International Business Machines Corporation | Dynamic connection capacity management |
CN109840144B (en) * | 2018-12-28 | 2023-09-19 | 航天信息股份有限公司 | Information service scheduling method and system for cross-mechanism batch service request |
US11277317B2 (en) * | 2019-08-05 | 2022-03-15 | International Business Machines Corporation | Machine learning to predict quality-of-service needs in an operational data management system |
CN110598155A (en) * | 2019-09-17 | 2019-12-20 | 北京锐安科技有限公司 | Ajax request calling method and device, computer equipment and storage medium |
CN111193774A (en) * | 2019-12-10 | 2020-05-22 | 天翼电子商务有限公司 | Method and system for improving throughput of server system and server system |
CN111538600B (en) * | 2020-02-25 | 2023-09-12 | 远景智能国际私人投资有限公司 | Message processing method, device, computer equipment and storage medium |
CN113342764A (en) * | 2021-06-12 | 2021-09-03 | 四川虹美智能科技有限公司 | Data synchronization method and device among different cloud servers |
US20240064207A1 (en) * | 2022-08-16 | 2024-02-22 | Capital One Services, Llc | Systems and methods for asynchronous and synchronous network communication |
CN117453422B (en) * | 2023-12-22 | 2024-03-01 | 南京研利科技有限公司 | Data processing method, device, electronic equipment and computer readable storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6321265B1 (en) * | 1999-11-02 | 2001-11-20 | Altavista Company | System and method for enforcing politeness while scheduling downloads in a web crawler |
US6442550B1 (en) * | 1999-12-14 | 2002-08-27 | International Business Machines Corporation | System and method in a collaborative data processing environment for customizing the quality of service on a per-client basis |
Family Cites Families (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2149445A1 (en) * | 1994-07-27 | 1996-01-28 | Aziza Bushra Faruqi | Separation and transmission control method and apparatus for a microkernal data processing system |
US6006247A (en) * | 1995-03-21 | 1999-12-21 | International Business Machines Corporation | Method and system for scheduling threads and handling exceptions within a multiprocessor data processing system |
US5774668A (en) * | 1995-06-07 | 1998-06-30 | Microsoft Corporation | System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing |
US5928323A (en) * | 1996-05-30 | 1999-07-27 | Sun Microsystems, Inc. | Apparatus and method for dynamically generating information with server-side software objects |
US6006274A (en) * | 1997-01-30 | 1999-12-21 | 3Com Corporation | Method and apparatus using a pass through personal computer connected to both a local communication link and a computer network for indentifying and synchronizing a preferred computer with a portable computer |
US6192389B1 (en) * | 1997-03-28 | 2001-02-20 | International Business Machines Corporation | Method and apparatus for transferring file descriptors in a multiprocess, multithreaded client/server system |
US5987454A (en) * | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
CA2220578A1 (en) * | 1997-11-10 | 1999-05-10 | Northern Telecom Limited | Distributed service network |
US6859451B1 (en) * | 1998-04-21 | 2005-02-22 | Nortel Networks Limited | Server for handling multimodal information |
US6189033B1 (en) * | 1998-07-16 | 2001-02-13 | Hewlett-Packard Company | Method and system for providing performance guarantees for a data service system of a data access network system |
US6304906B1 (en) * | 1998-08-06 | 2001-10-16 | Hewlett-Packard Company | Method and systems for allowing data service system to provide class-based services to its users |
US6480865B1 (en) * | 1998-10-05 | 2002-11-12 | International Business Machines Corporation | Facility for adding dynamism to an extensible markup language |
US6401126B1 (en) * | 1999-03-10 | 2002-06-04 | Microsoft Corporation | File server system and method for scheduling data streams according to a distributed scheduling policy |
US6691208B2 (en) * | 1999-03-12 | 2004-02-10 | Diva Systems Corp. | Queuing architecture including a plurality of queues and associated method for controlling admission for disk access requests for video content |
US6292792B1 (en) * | 1999-03-26 | 2001-09-18 | Intelligent Learning Systems, Inc. | System and method for dynamic knowledge generation and distribution |
US6031747A (en) * | 1999-08-02 | 2000-02-29 | Lockheed Martin Missiles & Space Company | Interleaved synchronous flyback converter with high efficiency over a wide operating load range |
US6880126B1 (en) * | 1999-08-03 | 2005-04-12 | International Business Machines Corporation | Controlling presentation of a GUI, using view controllers created by an application mediator, by identifying a destination to access a target to retrieve data |
US6732330B1 (en) * | 1999-09-30 | 2004-05-04 | International Business Machines Corporation | Scripting language blocks to support multiple scripting languages in a single web page |
US6718516B1 (en) * | 1999-09-30 | 2004-04-06 | International Business Machines Corporation | Method for verifying context between multiple related XML tags in document object model (DOM) |
US6516337B1 (en) * | 1999-10-14 | 2003-02-04 | Arcessa, Inc. | Sending to a central indexing site meta data or signatures from objects on a computer network |
US6779152B1 (en) * | 1999-12-07 | 2004-08-17 | International Business Machines Corporation | Method for rotating a dynamic HTML table |
WO2001042966A2 (en) * | 1999-12-13 | 2001-06-14 | Novient, Inc. | Attribute and application synchronization in distributed network environment |
US6421673B1 (en) * | 1999-12-13 | 2002-07-16 | Novient, Inc. | Method for mapping applications and or attributes in a distributed network environment |
US20010047385A1 (en) * | 1999-12-30 | 2001-11-29 | Jeffrey Tuatini | Passthru to shared service funtionality |
WO2001052090A2 (en) * | 2000-01-14 | 2001-07-19 | Saba Software, Inc. | Method and apparatus for a web content platform |
US7702995B2 (en) * | 2000-04-24 | 2010-04-20 | TVWorks, LLC. | Method and system for transforming content for execution on multiple platforms |
US6327628B1 (en) * | 2000-05-19 | 2001-12-04 | Epicentric, Inc. | Portal server that provides a customizable user Interface for access to computer networks |
US6763520B1 (en) * | 2000-08-24 | 2004-07-13 | Cognos Incorporated | Fair assignment of processing resources to queued requests |
EP1364313A2 (en) * | 2000-10-31 | 2003-11-26 | Michael Philip Kaufman | System and method for automatically generating user interfaces for arbitrarily complex or large databases |
US8364798B2 (en) * | 2001-01-23 | 2013-01-29 | Verizon Business Global Llc | Method and system for providing software integration for a telecommunications services on-line procurement system |
US7546576B2 (en) * | 2001-06-15 | 2009-06-09 | Lightsurf Technology, Inc. | Software framework for web-based applications |
US6948151B2 (en) * | 2001-06-29 | 2005-09-20 | International Business Machines Corporation | System and method for dynamic packaging of component objects |
US6886041B2 (en) * | 2001-10-05 | 2005-04-26 | Bea Systems, Inc. | System for application server messaging with multiple dispatch pools |
US6873984B1 (en) * | 2002-02-20 | 2005-03-29 | Oracle International Corporation | Data mining recommendation web beans and JSP tag libraries |
US7080379B2 (en) * | 2002-06-20 | 2006-07-18 | International Business Machines Corporation | Multiprocessor load balancing system for prioritizing threads and assigning threads into one of a plurality of run queues based on a priority band and a current load of the run queue |
-
2002
- 2002-10-03 US US10/264,439 patent/US6886041B2/en not_active Expired - Lifetime
- 2002-10-04 CN CNB028228723A patent/CN100342369C/en not_active Expired - Lifetime
- 2002-10-04 JP JP2003535082A patent/JP4287276B2/en not_active Expired - Lifetime
- 2002-10-04 WO PCT/US2002/031724 patent/WO2003032185A1/en active Application Filing
- 2002-10-04 EP EP02800901.7A patent/EP1438678B1/en not_active Expired - Lifetime
- 2002-10-04 AU AU2002362654A patent/AU2002362654B2/en not_active Expired
-
2005
- 2005-03-01 US US11/069,490 patent/US20050149612A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6321265B1 (en) * | 1999-11-02 | 2001-11-20 | Altavista Company | System and method for enforcing politeness while scheduling downloads in a web crawler |
US6442550B1 (en) * | 1999-12-14 | 2002-08-27 | International Business Machines Corporation | System and method in a collaborative data processing environment for customizing the quality of service on a per-client basis |
Non-Patent Citations (1)
Title |
---|
See also references of EP1438678A4 * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100347675C (en) * | 2004-06-29 | 2007-11-07 | 北京大学 | Property optimizing method for applying server |
EP1686763A1 (en) * | 2005-02-01 | 2006-08-02 | Microsoft Corporation | Access-limited buffer |
US7565395B2 (en) | 2005-02-01 | 2009-07-21 | Microsoft Corporation | Mechanism for preserving session state when using an access-limited buffer |
JP2008533630A (en) * | 2005-03-21 | 2008-08-21 | デクステラ・インコーポレイテッド | Data management for mobile data systems |
JP2008536210A (en) * | 2005-03-21 | 2008-09-04 | デクステラ・インコーポレイテッド | Module application for mobile data systems |
JP2008537818A (en) * | 2005-03-21 | 2008-09-25 | デクステラ・インコーポレイテッド | Adapter architecture for mobile data systems |
GB2429086A (en) * | 2005-08-10 | 2007-02-14 | Symbian Software Ltd | Improving the efficiency of file server requests in a computing device |
GB2507294A (en) * | 2012-10-25 | 2014-04-30 | Ibm | Server work-load management using request prioritization |
US9571418B2 (en) | 2012-10-25 | 2017-02-14 | International Business Machines Corporation | Method for work-load management in a client-server infrastructure and client-server infrastructure |
US11330047B2 (en) | 2012-10-25 | 2022-05-10 | International Business Machines Corporation | Work-load management in a client-server infrastructure |
CN112612586A (en) * | 2020-12-24 | 2021-04-06 | 大唐互联科技(武汉)有限公司 | Method and system for designing connection equipment based on reactive architecture |
Also Published As
Publication number | Publication date |
---|---|
JP4287276B2 (en) | 2009-07-01 |
US20050149612A1 (en) | 2005-07-07 |
US20030093499A1 (en) | 2003-05-15 |
AU2002362654B2 (en) | 2008-03-06 |
CN100342369C (en) | 2007-10-10 |
US6886041B2 (en) | 2005-04-26 |
EP1438678A4 (en) | 2009-07-29 |
EP1438678B1 (en) | 2016-11-16 |
CN1589442A (en) | 2005-03-02 |
EP1438678A1 (en) | 2004-07-21 |
JP2005505833A (en) | 2005-02-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2002362654B2 (en) | System for application server messaging with multiple dispatch pools | |
AU2002362654A1 (en) | System for application server messaging with multiple dispatch pools | |
EP1438674B1 (en) | System for integrating java servlets with asynchronous messages | |
AU2002362656A1 (en) | System for integrating java servlets with asynchronous messages | |
US8082318B2 (en) | Controlling service requests transmitted from a client to a server | |
EP1235150B1 (en) | Apparatus and method for processing servlets | |
US6446204B1 (en) | Method and apparatus for implementing an extensible authentication mechanism in a web application server | |
US7882501B1 (en) | System and method for enabling dynamic modifed class reloading in an application server environment | |
WO2001013227A2 (en) | System and method for enabling application server request failover | |
EP1564635A2 (en) | Scalable print spooler | |
WO2001013228A9 (en) | Graceful distribution in application server load balancing | |
US9231995B2 (en) | System and method for providing asynchrony in web services | |
US20050030555A1 (en) | Job processing framework | |
Schmidt et al. | Architectures and patterns for developing high-performance, real-time ORB endsystems | |
EP1784720A2 (en) | Method and system for reading data, related network and computer program product therefor | |
Stal et al. | Efficient Architectures for object-oriented component-based Middleware |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG UZ VN YU ZA ZM |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003535082 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002362654 Country of ref document: AU |
|
REEP | Request for entry into the european phase |
Ref document number: 2002800901 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002800901 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 955/CHENP/2004 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20028228723 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2002800901 Country of ref document: EP |