CN118069241A - Management system and method for concurrent JAVA application program - Google Patents

Abstract

The invention discloses a management system and a method for concurrent JAVA application programs, wherein the system comprises the following steps: the interface module is used for acquiring the data information of the currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program; the judging module is used for judging the state of each JAVA application program based on the state information; the states include a normal state and an abnormal state: the processing module responds to the abnormal state and classifies the abnormal state; calling a preset processing strategy to process based on the obtained classification result so as to realize exception handling of the JAVA application program; the effect is that: the distinguishing of each JAVA application program is realized by acquiring the process information and the state information of each JAVA application program; and then when an abnormality occurs, a preset processing strategy is called for processing so as to realize the abnormality processing, thereby improving the timeliness of the problem processing.

Description

Management system and method for concurrent JAVA application program

Technical Field

The invention relates to the technical field of computers, in particular to a management system and method for concurrent JAVA application programs.

Background

JAVA is a widely used language, and has the characteristics of cross-platform property and easy learning and use, and many server applications are developed by adopting the JAVA language.

In the application of Java applications, there are cases where a plurality of Java applications need to be run simultaneously, and concurrent execution is sometimes performed. Since Java applications are run by Java Virtual Machines (JVMs), each Java application will launch a corresponding Java process; under Windows running environment, these Java processes are Java. Exe, so that the running state of each program cannot be effectively monitored, and the problem that the running state cannot be processed in time after an error occurs is caused.

Disclosure of Invention

In view of the foregoing, in order to overcome the shortcomings in the prior art, an object of the present invention is to provide a management system and method for concurrent JAVA applications.

To achieve the above object, in a first aspect, the present invention provides a management system for concurrent JAVA applications, the system comprising:

the interface module is used for acquiring the data information of the currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

The judging module is used for judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state:

a processing module for:

Responding to the abnormal state and classifying the abnormal state;

and calling a preset processing strategy to process based on the obtained classification result so as to realize exception processing of the corresponding JAVA application program.

As a preferred embodiment of the present application, the determining module is further configured to:

acquiring detailed information of a corresponding process based on the process information;

and searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not.

As a preferred embodiment of the present application, classifying the abnormal state includes:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

In a preferred embodiment of the present application, the calling a preset processing policy to process based on the obtained classification result specifically includes:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters;

when the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrading.

As a preferred embodiment of the present application, the processing module is further configured to:

Controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.

In a second aspect, a method for managing concurrent JAVA applications is applied to the management system for concurrent JAVA applications described in the first aspect, and the method includes:

Acquiring data information of a currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

Judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state:

Responding to the abnormal state and classifying the abnormal state;

and calling a preset processing strategy to process based on the obtained classification result so as to realize exception processing of the corresponding JAVA application program.

As a preferred embodiment of the present application, the method further comprises:

acquiring detailed information of a corresponding process based on the process information;

and searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not.

As a preferred embodiment of the present application, classifying the abnormal state includes:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

In a preferred embodiment of the present application, the calling a preset processing policy to process based on the obtained classification result specifically includes:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters;

when the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrading.

As a preferred embodiment of the present application, the method further comprises: controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.

By adopting the technical scheme, the management system and the method for the concurrent JAVA application provided by the invention realize the distinction of each JAVA application by acquiring the process information and the state information of each JAVA application; the running state of each program is effectively monitored by utilizing the state information, and the state of each JAVA application program is judged; and then when an abnormality occurs, calling a preset processing strategy to process based on the obtained classification result so as to realize the abnormality processing of the corresponding JAVA application program, thereby improving the timeliness of problem processing.

Drawings

Fig. 1 is a system block diagram of a management system for concurrent JAVA applications according to an embodiment of the present invention;

Fig. 2 is a flowchart of a method for managing concurrent JAVA applications according to an embodiment of the present invention.

Detailed Description

Specific embodiments of the invention will be described in detail below, it being noted that the embodiments described herein are for illustration only and are not intended to limit the invention. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that: no such specific details are necessary to practice the invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the application herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the present application, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal" and the like indicate an azimuth or a positional relationship based on that shown in the drawings. These terms are only used to better describe the present application and its embodiments and are not intended to limit the scope of the indicated devices, elements or components to the particular orientations or to configure and operate in the particular orientations.

Also, some of the terms described above may be used to indicate other meanings in addition to orientation or positional relationships, for example, the term "upper" may also be used to indicate some sort of attachment or connection in some cases. The specific meaning of these terms in the present application will be understood by those of ordinary skill in the art according to the specific circumstances.

Throughout the specification, references to "one embodiment," "an embodiment," "one example," or "an example" mean: a particular feature, structure, or characteristic described in connection with the embodiment or example is included within at least one embodiment of the invention. Thus, the appearances of the phrases "in one embodiment," "in an embodiment," "one example," or "an example" in various places throughout this specification are not necessarily all referring to the same embodiment or example. Furthermore, the particular features, structures, or characteristics may be combined in any suitable combination and/or sub-combination in one or more embodiments or examples.

It should be noted that technical terms of the present embodiment are the common meanings understood in the art unless otherwise specified.

As shown in fig. 1, a management system for concurrent JAVA applications according to an embodiment of the present invention includes:

the interface module is used for acquiring the data information of the currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

The judging module is used for judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state:

a processing module for:

Responding to the abnormal state and classifying the abnormal state;

and calling a preset processing strategy to process based on the obtained classification result so as to realize exception processing of the corresponding JAVA application program.

In implementation, the system is deployed on a windows server and is provided with a JDK command line tool and a command line tool corresponding to a windows operating system.

Obtaining the PID of the Java program by using the RuntimeMXBean interface provided by MANAGEMENT FACTORY classes; and taking the PID as the process information.

Firstly, runtimeMXBean objects are obtained, then, character strings containing the PID are obtained through a getName () method of the objects, and finally, the PID is extracted from the character strings.

The state information is obtained using the following commands in the JDK command line tool.

Jps (JVM Process Status), the user is used for checking the starting class, the input parameters, the Java virtual machine parameters and other information of all Java processes;

jstat (JVM Statistics Monitoring Tool) the method is used for collecting operation data of all aspects of the HotSpot virtual machine, including displaying operation data such as class information, memory, garbage collection, JIT compiling and the like in a local or remote virtual machine process;

jinfo (Configuration Info for Java): configuration Info forJava, displaying virtual machine configuration information; checking and adjusting various parameters; parameters of jvm may be dynamically modified without restarting the virtual machine through use of jinfo;

jstack (STACK TRACE for Java) generating a thread snapshot of the current moment of the virtual machine, wherein the thread snapshot is a set of method stacks which are being executed by each thread in the current virtual machine;

the purpose of generating the thread snapshot is mainly to locate the reason that the thread is stopped for a long time, such as deadlock among threads, dead loop, long-time waiting caused by requesting external resources, and the like, which are all the reasons that the thread is stopped for a long time; by looking at the call stack of each thread jstack, it is possible to know what the thread that has not responded does in the background at all, or what resources are waiting.

Further, by obtaining a list of startup parameters again using the getInputArguments () method, by examining the startup parameters, the parameters containing the application identifier are found.

In this way, each process is accurately identified and managed.

Further, in order to implement management of concurrent applications, in another embodiment, on the basis of the above technical solution, the determining module is further configured to:

acquiring detailed information of a corresponding process based on the process information;

and searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not.

Specifically, detailed information of the process is obtained through a command line tool of an operating system; whether the process is a background process or not is judged by searching whether the process detailed information contains a keyword 'java. Exe'.

Further, classifying the abnormal state includes:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

Specifically, by calling monitoring and diagnostic tools provided by the operating system and the Java virtual machine, the states inside the system resources and the Java services are obtained, and which are normal and which are abnormal are identified.

Further, the step of calling a preset processing strategy for processing based on the obtained classification result specifically comprises the following steps:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters; when restarting, the breakpoint resuming is also carried out based on the record in the log information, so that the integrity and the correctness of the data are ensured;

the JVM parameters include adjusting memory allocation parameters, thread number parameters, and the like.

When the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrade; the resource release is that when a certain object is not used any more, the resource is released in time, including closing a file, connecting a database and stopping a thread used;

The size of the heap memory is adjusted, including the size of the heap memory is increased, and garbage collection operation is triggered;

version upgrades, by repairing some existing bugs, to reduce the occurrence of failures.

If yes, service migration is carried out, and modes such as operating disk, program configuration and the like are modified; the tracking tool provided by the system can be called to judge whether the parameters, the return value, the calling time and the like of each API call can be detected; thereby confirming whether the interaction is normal.

In this embodiment, the distinction of each JAVA application is achieved by acquiring process information and state information of each JAVA application; the running state of each program is effectively monitored by utilizing the state information, and the state of each JAVA application program is judged; and then when an abnormality occurs, calling a preset processing strategy to process based on the obtained classification result so as to realize the abnormality processing of the corresponding JAVA application program, thereby improving the timeliness of problem processing.

Further, in order to obtain an optimal operation effect for different systems, in another embodiment, based on the above technical solution, the processing module is further configured to:

Controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.

Specifically, the configuration resources comprise data such as the number of cores of a CPU, an operating system, a memory, a JDK version and the like;

Or directly based on the number of resources needed and the total number of resources.

Based on the same inventive concept, referring to fig. 2, an embodiment of the present invention further provides a management method for concurrent JAVA applications, applied to the management system for concurrent JAVA applications described in the first aspect, where the method includes:

s101, acquiring data information of a currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

s102, judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state;

S103, responding to the abnormal state and classifying the abnormal state;

s104, based on the obtained classification result, calling a preset processing strategy to process so as to realize the exception processing of the corresponding JAVA application program.

Wherein classifying the abnormal state includes:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

And calling a preset processing strategy to process based on the obtained classification result, wherein the method specifically comprises the following steps of:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters;

when the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrading.

Further, the embodiment of the present invention also provides another method for managing concurrent JAVA applications, which is different from the foregoing method embodiment in that the method further includes:

acquiring detailed information of a corresponding process based on the process information;

searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not;

the method further comprises the steps of:

Controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.

It should be noted that, specific implementation steps and beneficial effects in the method embodiments may refer to the description of the foregoing system embodiments, and are not repeated herein.

The distinguishing of each JAVA application program is realized by acquiring the process information and the state information of each JAVA application program; the running state of each program is effectively monitored by utilizing the state information, and the state of each JAVA application program is judged; and then when an abnormality occurs, calling a preset processing strategy to process based on the obtained classification result so as to realize the abnormality processing of the corresponding JAVA application program, thereby improving the timeliness of problem processing.

The embodiment of the invention also provides a computer readable storage medium storing a computer program, the computer program comprising program instructions which when executed by a processor realize: the management method for the concurrent JAVA application.

It should be appreciated that in embodiments of the present invention, the Processor may be a central processing unit (Central Processing Unit, CPU), which may also be other general purpose Processor, digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the several embodiments provided by the present application, it should be understood that the disclosed systems and methods may be implemented in other ways. For example, the system embodiments described above are merely illustrative, e.g., the division of the modules is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present invention.

In addition, each functional module in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims (10)

1. A management system for concurrent JAVA applications, the system comprising:

the interface module is used for acquiring the data information of the currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

The judging module is used for judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state:

a processing module for:

Responding to the abnormal state and classifying the abnormal state;

and calling a preset processing strategy to process based on the obtained classification result so as to realize exception processing of the corresponding JAVA application program.

2. The system according to claim 1, wherein said determining module is further configured to:

acquiring detailed information of a corresponding process based on the process information;

and searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not.

3. The system for managing concurrent JAVA applications according to claim 1, wherein classifying the abnormal state comprises:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

4. A system for managing concurrent JAVA applications according to claim 3, wherein said invoking a preset processing policy for processing based on the obtained classification result specifically comprises:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters;

when the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrading.

5. The system for managing concurrent JAVA applications according to claim 2, wherein said processing module is further configured to:

Controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.

6. A method for managing concurrent JAVA applications, applied to a management system for concurrent JAVA applications according to claim 1, the method comprising:

Acquiring data information of a currently running JAVA virtual machine process; the data information comprises process information and state information of each JAVA application program;

Judging the state of each JAVA application program based on the state information; wherein the states include a normal state and an abnormal state:

Responding to the abnormal state and classifying the abnormal state;

and calling a preset processing strategy to process based on the obtained classification result so as to realize exception processing of the corresponding JAVA application program.

7. The method for managing concurrent JAVA applications according to claim 6, further comprising:

acquiring detailed information of a corresponding process based on the process information;

and searching and judging the detailed information by combining with preset keywords to judge whether the process is a background process or not.

8. The method of claim 1, wherein classifying the exception state comprises:

Dividing the abnormal state into system abnormality and JAVA service abnormality;

The system abnormality is judged based on the CPU occupation rate, the memory margin and the network link number;

and judging the JAVA service abnormality based on the JAVA heap, the abnormality information in the log, the lock condition and the call stack information of each thread.

9. The method for managing concurrent JAVA applications according to claim 8, wherein the invoking the preset processing policy for processing based on the obtained classification result specifically comprises:

When the system is abnormal, the preset processing strategy comprises restarting the program to release the occupied system resources; adjusting JVM parameters;

when the JAVA service is abnormal, the preset processing strategy comprises resource release, adjustment of the size of a heap memory and version upgrading.

10. The method for managing concurrent JAVA applications according to claim 7, further comprising: controlling the number of concurrent threads by using a thread pool; the threads in the thread pool are all background threads; the size of the thread pool is calculated based on the configured resources of the system.