System and method for managing code displacement

• US 9,274,921 B2
• Filed: 12/27/2006
• Issued: 03/01/2016
• Est. Priority Date: 12/27/2006
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Alcott, Thomas J., Bhogal, Kulvir Singh, McGee, Jason Robert, Polozoff, Alexandre
• Primary Examiner(s): BROPHY, MATTHEW J
• Application Number:
  US11/616,400
• Publication Number:
  US 20080163169A1
• Time in Patent Office: 3,352 Days
• Field of Search: 717120-121, 709/226
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups

Abstract

A system for managing code displacement may include a manager and an application operable on a server. The application may include a plurality of modules each module for performing a different operation. The system may also include priority information associated with each module to permit the manager to deactivate selected ones of the modules based on the priority information to improve performance of the application.

Claims

1. A system for managing code displacement, comprising:

an application server;

a manager operable on the application server;

an application operable on the application server, wherein the application includes a plurality of modules each to perform a different operation and wherein the manager monitors a load or traffic level on the application; and

priority information associated with each module to permit the manager to deactivate selected ones of the modules based on the priority information to improve performance of the application in response to the load or traffic level exceeding a predetermined threshold, wherein the manager is configured to determine which modules of the plurality modules are available for deactivation by injecting an alternate code in response to the load or traffic level exceeding the predetermined threshold and to determine which modules of the plurality of modules to deactivate by injecting a default no operation (NOP) code in response to none of the modules of the plurality of modules being available for deactivation by injecting the alternate code.

2. The system of claim 1, further comprising a type of replacement associated with each module.

3. The system of claim 2, wherein the type of replacement comprises one of a no operation (NOP) type function and a cached return value function to be returned in response to a deactivated module being called and wherein this type of replacement is associated with the deactivated module.

4. The system of claim 1, wherein the priority information comprises a level of desirability for the associated module to execute based on an importance of the associated module to the application.

5. The system of claim 4, further comprising a property file including an identity of each module, the importance associated with each module, and a type of replacement associated with each module.

6. The system of claim 1, further comprising a code injection to be injected to disable a selected module in response to a load or traffic level on the application exceeding the predetermined threshold, and wherein the code injection is removed to reactivate the selected module in response to the load or traffic level falling below the predetermined threshold.

7. The system of claim 1, wherein the manager comprises a data structure to inject and remove the code injection from the selected module.

8. A method for managing code displacement, comprising:

monitoring a load or traffic level on a software application operating on a server, wherein the software application includes a plurality of modules;

determining which modules of the plurality of modules are available for deactivation by injecting an alternate code in response to the load or traffic level on the application exceeding a predetermined threshold;

determining which modules of the plurality of modules to deactivate by injecting a default no operation (NOP) code in response to none of the modules of the plurality of modules being available for deactivation by injecting the alternate code; and

deactivating a selected number of modules based on a predetermined basis associated with each module in response to the load or traffic level on the application exceeding the predetermined threshold.

9. The method of claim 8, further comprising reactivating a chosen number of modules based on the predetermined basis in response to the load or traffic level falling below a preset threshold.

10. The method of claim 9, wherein the predetermined basis comprises at least one of a priority of operation of the module, a level of importance of the module to the application, and a desirability of execution of the module during operation of the application.

11. The method of claim 8, further comprising determining a type of replacement associated with each module to be returned in response to a deactivated module being called.

12. The method of claim 8, further comprising returning one of a group of types of replacements including a no operation (NOP) type function and a cached return value function, in response to a deactivated module being called and one of these types of replacements being associated with the deactivated module.

13. The method of claim 8, further comprising:

injecting a code injection to deactivate each module; and

removing the code injection to reactivate each module in response to the load or traffic level falling below a preset threshold.

14. The method of claim 8, further comprising determining a type of code to be injected to deactivate a particular module.

15. The method of claim 14, wherein determining the type of code comprises determining one of a group comprising an NOP code, a cache return value code and an alternate code.

21. The method of claim 8, further comprising adding an identity of each deactivated module to a list of deactivated modules.

22. The method of claim 8, further comprising:

providing the alternate code by the software application; and

generating the default NOP code by the server.

23. The method of claim 22, wherein providing the alternate code by the software application comprises reloading original code with the alternate code by a one classloader of multiple classloaders, wherein the software application points to the one classloader that has the desired alternate code.

16. A computer program product for managing code displacement, the computer program product comprising:

a computer usable storage medium having computer usable program code embodied therein, the computer usable medium comprising;

computer usable program code configured to monitor a load or traffic level on a software application, wherein the application includes a plurality of modules;

computer usable program code configured to determine which modules of the plurality of modules are available for deactivation by injecting an alternate code in response to the load or traffic level on the application exceeding a predetermined threshold;

computer usable program code configured to determine which modules of the plurality of modules to deactivate by injecting a default no operation (NOP) code in response to none of the modules of the plurality of modules being available for deactivation by injecting the alternate code; and

computer usable program code configured to deactivate a selected number of modules based on a predetermined basis associated with each module in response to the load or traffic level on the application exceeding the predetermined threshold.

17. The computer program product of claim 16, wherein the computer usable medium further comprises computer usable program code configured to reactivate a chosen number of modules based on the predetermined basis in response to the load or traffic level falling below a preset threshold.

18. The computer program product of claim 16, wherein the computer usable medium further comprises computer usable program code configured to determine a type of replacement associated with each module to be returned in response to a deactivated module being called.

19. The computer program product of claim 16, wherein the computer usable medium further comprises:

computer usable program code configured to inject a code injection to deactivate each module; and

computer usable program code configured to remove the code injection to reactivate each module in response to the load or traffic level falling below a preset threshold.

20. The computer program product of claim 16, wherein the computer usable medium further comprises computer usable program code configured to determine a type of code to be injected to deactivate a particular module.