Application Server Overload Protection via Priority-Based Request Rejection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Application servers often become overloaded, leading to poor performance and stability, as existing methods fail to characterize requests and reject those that would take longer than one minute, exacerbating the issue and not providing effective overload protection.
Innovation Solution
A system that generates customizable rejection messages and prioritizes requests using a priority queue, determining the workload manager and servlet for each request, and specifies thresholds to manage overload conditions efficiently, even within a single server, thereby preventing further strain on the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the server accepts all incoming requests during overload, then the server processes more work, but the server performance deteriorates and stability is lost
Solution Approach 1:
The patent applies local quality by implementing priority-based request handling where different requests receive different treatment based on their priority level. High-priority requests (e.g., payment processing) are serviced while low-priority requests (e.g., browsing) are rejected during overload, allowing the server to maintain stability while still processing critical work.
Solution Approach 2:
The system dynamically changes the parameter of request acceptance based on server load conditions. When overload is detected, the server transitions from accepting all requests to selectively accepting only high-priority requests, thereby maintaining stability while preserving essential productivity.
2Reliability
If the server rejects all requests during overload, then server stability is maintained, but no useful work is processed including high-priority requests
Solution Approach 1:
Instead of uniform rejection, the patent implements differentiated treatment where high-priority requests are serviced and low-priority requests are rejected. This allows the server to maintain stability while continuing to process critical work, resolving the contradiction between stability and productivity.
3Adaptability or versatility
If the server uses complex request characterization and filtering, then request prioritization improves, but processor overhead increases during overload
Solution Approach 1:
The patent applies partial action by implementing lightweight request characterization that focuses only on essential priority determination rather than comprehensive request analysis. This provides sufficient adaptability for overload management while minimizing processor overhead during critical periods.
4Quantity of substance
If the server places requests in a fixed-length queue, then request buffering is provided, but requests that take longer than one minute are not rejected and continue to strain the server
Solution Approach 1:
The patent implements preliminary action by evaluating request priority before queuing and by setting maximum processing time limits. Requests that exceed the time threshold are automatically rejected, preventing them from continuing to strain the server while still providing buffering for acceptable requests.
Data Source
AI summary
A system and method for application server with overload protection. A system, for example a server or a cluster, is designed to generate a message, and/or reject further work, whenever the server becomes overloaded. It does this in a processor-efficient manner so as not to place even more strain on the already burdened server. The rejection message or action is customizable. In accordance with an embodiment, the system determines where the request would appear in a priority queue, and rejects those further down the queue. It does this quickly and with minimal processing time by determining to which workload manager the request is going to be delivered.