TWI517045B - JAVA cluster application system code loading and upgrading devices and methods - Google Patents

Description

JAVA cluster application system code loading and upgrading device and method

The present application relates to the field of network technologies, and in particular, to a JAVA cluster application system code loading apparatus and method.

A cluster system is a cluster system that is connected by multiple isomorphic or heterogeneous computers to accomplish specific tasks. The JAVA cluster application system is a JAVA application system based on cluster deployment.

General JAVA cluster application systems, such as JAVA's web application system, task clustering system, etc., need to install and deploy the category libraries required for system operation on the client side. Once the code or category library needs to be upgraded, the latest code updates need to be posted to all servers in the cluster and the java application on each server is restarted.

The inventor found through research that the existing JAVA cluster application system, whether it is code loading or code upgrade, needs to release the newly loaded or updated code updates to all servers in the cluster, and restart each servo. The java application on the device is huge, time consuming, and very inefficient.

In view of this, the purpose of the embodiments of the present application is to provide a JAVA cluster application system code loading apparatus and method, which implements loading and upgrading of codes quickly and efficiently.

In order to achieve the above objective, the embodiment of the present application provides the following technical solution: a JAVA cluster application system code loading device, located in the JAVA cluster server, comprising: a receiving unit, configured to receive a category sent by the server In the request, the category loading request carries the category name of the first JAVA category to be loaded; the searching unit is configured to search, according to the category name, the storage address of the entity of the first JAVA category from the category registration information, according to the category name The storage address obtains the latest version number of the first JAVA category from the storage location of the first JAVA category; the determining unit is configured to determine the latest version number of the first JAVA category and the last stored version of the local storage Whether the version number of a JAVA category is the same; the processing unit is configured to: when the latest version number of the first JAVA category is different from the locally stored version number of the first JAVA category that was last loaded from the first JAVA category Storing the latest version of the first JAVA category, loading, and updating the first JAVA category in the version version record; otherwise directly loading the first JAV Category A.

Optionally, the content in the category registration information is recorded in the search unit by using a category address hash table.

Optionally, the category name of the first JAVA category is recorded by the primary key of the category address hash table, and the first JAVA category storage address is recorded by the value of the primary key of the category address hash table.

Optionally, the searching unit records the version information of the first JAVA category by using a category version hash table.

Optionally, the category name of the first JAVA category is recorded by the primary key of the category version hash table, and the version number of the first JAVA category that was last loaded is recorded by the value of the primary key of the category version hash table.

A category library registration system for maintaining category registration information, the system comprising: an obtaining unit, configured to obtain a JAVA category library according to the received JAVA category library storage address; and a new unit for traversing the JAVA category library, A new category included in the JAVA category library is inserted into the category registration information, and an update unit is used to traverse the JAVA category library according to each JAVA category recorded in the JAVA category library. The storage address updates the storage address of the corresponding JAVA category in the registration information.

The category registration information includes the category name, the category library name, and the category library storage address.

A JAVA cluster application system code loading method is used in the server of the JAVA cluster, comprising: receiving a category loading request sent by a server, where the category loading request carries a category of a first JAVA category to be loaded Searching for the first JAVA category storage address from the category registration information according to the category name, and obtaining the latest version number of the first JAVA category from the storage location of the first JAVA category according to the storage address; determining the first The latest version number of the JAVA category is the same as the last stored version number of the first JAVA category stored locally; when the latest version number is the same as the version number of the first JAVA category that was last stored locally stored Obtaining the latest version of the first JAVA category, loading, and updating the first JAVA category in the version version record; otherwise, directly loading the first JAVA category.

A class library registration method includes: obtaining a JAVA class library according to the received JAVA class library storage address; traversing the JAVA class library, and classifying the new category in the JAVA class library that is not yet recorded in the category registration information. Inserting the category registration information; traversing the JAVA category library, and updating the storage address of the corresponding JAVA category in the registration information according to the storage address of each JAVA category recorded in the JAVA category library.

It can be seen that, in the embodiment of the present application, the receiving unit is configured to receive a category loading request sent by the server, where the category loading request carries a category name of the first JAVA category to be loaded, and a searching unit, configured to The category name is used to search for the storage address of the entity of the first JAVA category from the category registration information, and obtain the latest version number of the first JAVA category from the storage location of the first JAVA category according to the storage address; Determining whether the latest version number of the first JAVA category is the same as the last stored version number of the first JAVA category stored locally; the processing unit is configured to store the latest version number of the first JAVA category with the local version When the version number of the first JAVA category that was last loaded is different, the latest JAVA category is obtained from the storage location of the first JAVA category, and the first JAVA category is recorded in the category version. The version number is updated; otherwise the first JAVA category is loaded directly. The loading scheme provided by the embodiment of the present application does not need to publish the latest code to each server in the cluster, nor does it need to restart the Java application of the cluster server, and only needs to store the code in a server, such as an SVN server. The code is updated, and each server located in the cluster can automatically load the latest code, which improves the usability of the JAVA cluster system.

In order to enable a person skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. The described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope should fall within the scope of the present application.

FIG. 1 is a schematic structural diagram of an apparatus for code loading of a JAVA cluster application system according to an embodiment of the present application, where the apparatus is located in each server of the JAVA cluster. The device includes: a receiving unit 101, a searching unit 102, a determining unit 103, and a processing unit 104, wherein: the receiving unit 101 is configured to receive a category loading request sent by the server, where the category loading request carries the to-be-loaded The category name of a JAVA category; the first JAVA category is used to refer to the JAVA category to be loaded in the category load request. For example, a JAVA category to be loaded may be com.foo.helloworld.

The searching unit 102 is configured to search the first JAVA category storage address from the category registration information according to the category name, and obtain the latest version number of the first JAVA category from the storage location of the first JAVA category according to the storage address; The category registration information can be recorded through a form. For example, in an embodiment of the present application, the category registration information is recorded through a category registry.

The ClassTable can be stored in the database to record the JAVA category and the storage address of each JAVA category. FIG. 2 is a schematic diagram of an application scenario of an apparatus provided in an embodiment of the present application. In the figure, the category registry is stored in 201, and the 203 of the code 202 provided in the embodiment of the present application is connected to the database 201, and the loading device 202 can communicate with the database 201 to read the category in the database 201. Registry information.

The JAVA category is generally packaged in a compressed package in jar format. The embodiment of the present application still adopts this manner. Referring to FIG. 2, in the embodiment of the present application, after the JAVA category is packaged into a jar package, the jar package is uploaded to 204. Save the jar package through the SVN server and record the version information of each jar package. SVN (Subversion) is a popular source version control system. SVN server is the server that Subversion uses to store and manage source code. Each jar package stored on the SVN server will have an SVN address, and the jar package can be searched according to the SVN address.

In FIG. 2, the server 203 is connected to the database 201. The loading device 202 located in the server 203 is capable of communicating with the SVN server, and each JAVA class is obtained from the SVN server according to the address of each jar package.

Table 1 is an example of a category registry provided by an embodiment of the present application. The information recorded in the category registry includes a JAVA category name, a name of a jar package to which the JAVA category belongs, and an SVN corresponding to the jar package to which the JAVA category belongs. address.

The name of the JAVA category given in the example in Table 1 is: com.foo.helloworld; the name of the jar package to which the JAVA category belongs is hello-biz; the SVN address corresponding to the jar package to which the JAVA category belongs is: http: //svn.foo-inc.com/repos/example/hello.jar.

The SVN server records every update to the JAVA category. Each time the user modifies the JAVA code and submits the modified JAVA code to the SVN server through the SVN client software, the SVN server generates a new version for the modified JAVA code and records the new version. In practical applications, each version of the JAVA code can be recorded by the version number. For the same JAVA category, the newer version will be the corresponding version number. For example, a JAVA category, its current version number is 15516. If a user modifies this JAVA category and submits the changes to the SVN server, the SVN server will upgrade the version number to 15517, and the original version of 15516. Become a historical version.

In order to improve the speed of searching for data, in some embodiments of the present application, the searching unit may record the address information and version information of the first JAVA category through the category address hash table and the category version hash table, respectively.

Specifically, the category name of the first JAVA category may be recorded by the primary key of the category address hash table, and the storage address of the first JAVA category is recorded by the value of the primary key of the category address hash table primary key.

Table 2 shows a category address hash table. As can be seen from the table, the JAVA category is packaged in the jar package, and the jar package is stored on the SVN server. The category address hash table records the category name through the primary key (key). In the table 2, the category name is com.foo.helloworld; the value of the primary key of the primary key is used to record the SVN address of the jar package to which the JAVA category belongs, Table 2 Medium, the address is

Http://svn.foo-inc.com/repos/example/helloworld.jar.

Table 3 is a category version hash table, the primary key (key) is used to record the category name, in Table 3, the category name is com.foo.helloworld; the value of the primary key (value) is used to record the jar package to which the JAVA category belongs. The loaded SVN version number, in Table 3, the last loaded version number of the jar package to which the com.foo.helloworld category belongs is: 22162.

The determining unit 103 is configured to determine whether the latest version number of the first JAVA category is the same as the version number of the first JAVA category that is stored locally last time; the category registration information records information of all the registered categories. In the embodiment of the present application, the address and version information of the category used by the local JAVA application is recorded through the category version hash table and the category address hash table.

The processing unit 104 is configured to: when the latest version number of the first JAVA category is different from the locally stored version number of the first JAVA category that was last loaded, obtain the latest version from the storage location of the first JAVA category The first JAVA category is loaded, and the first JAVA category is updated in the version number of the category version record; otherwise the first JAVA category is directly loaded.

Each time the processing unit loads the category, it will judge whether the jar package of the category is updated on the SVN through the category version number. If there is an update, update the corresponding version number in the category version hash table in the search unit to the latest version. The value of the primary key.

In the embodiment of the present application, if a JAVA category has been loaded and the version is consistent, the category loading device loads the category directly from the local and runs; if the versions are inconsistent, the server needs to be obtained from the server. The latest version of the JAVA category, loaded and run.

Referring to FIG. 3, when the loading device provided by the embodiment of the present application packs the JAVA category in a compressed package in a jar format, and the jar package is stored in the SVN server, the processing unit shown in FIG. 1 specifically includes: The first obtaining sub-unit 301 is configured to obtain the latest version of the jar to which the first JAVA category belongs when the latest version number of the first JAVA category is different from the locally stored version number of the first JAVA category that was last loaded. The SVN address corresponding to the packet; the second obtaining sub-unit 302 is configured to obtain the latest JAVA category according to the SVN address; the first processing sub-unit 303 is configured to load the first JAVA category, and The first JAVA category is updated in the version number record; the second processing sub-unit 304 is configured to directly directly when the latest version number is the same as the locally stored version number of the first JAVA category that was last loaded Load the first JAVA category.

The existing code loading scheme requires frequent uploading of the latest code to each server of the cluster, which is time consuming and wastes manpower and material resources. Especially in the case of a large number of cluster servers, the efficiency of code loading is even lower. The loading device provided by the embodiment of the present application does not need to publish the latest code to each server in the cluster, nor does it need to restart the Java application of the cluster server, and only needs to store the code in a server, such as an SVN server. The code is updated, and each server located in the cluster can automatically load the latest code, which improves the usability of the JAVA cluster system and improves the efficiency of code loading.

In addition, in the existing code loading scheme, if the code leak of some servers in the cluster is upgraded during the program loading process, or some server code upgrade fails, the servers in the cluster will appear. The simultaneous operation of different versions of new and old codes may damage the data and cause irreversible and serious consequences. The code loading device provided in the embodiment of the present application enables each server to update according to a code storage server, such as a code in the SVN server, to ensure that each server can automatically load into the latest version, thereby avoiding Because each server generates the destruction of data due to the simultaneous operation of different versions of the code, it avoids the serious consequences of irreversibility and improves the security of the entire JAVA integrated application system.

In order to further ensure that the loading device can obtain accurate and most comprehensive category information from the category registry, the embodiment of the present application further provides a category library registration system, which is specifically used to maintain the category registry, see FIG. 4, the category library registration The system includes: an obtaining unit 401, configured to obtain a JAVA category library according to the received JAVA category library storage address; a new unit 402, configured to traverse the JAVA category library, and include the unregistered in the category registry The new category in the JAVA category library is inserted into the category registry; the updating unit 403 is configured to traverse the JAVA category library, and update the corresponding JAVA in the registry according to the storage address of each JAVA category recorded in the JAVA category library. The storage address of the category.

The category library registration system provided by the embodiment of the present application can instantly record the new category in the JAVA category library into the category registry, and can also be used in the JAVA category that has been recorded in the category registry, and can also be in the JAVA category library. The storage address of each JAVA category is updated to update the storage address of the corresponding JAVA category in the registry, so as to ensure that the latest and most complete JAVA category information is always recorded in the category registry, and the loading device is loaded. Provide a strong guarantee.

The embodiment of the present application further provides a method for code loading of a JAVA cluster application system. In the server for the JAVA cluster, referring to FIG. 5, the method includes: S501, receiving a category loading request sent by a server, the category The loading request carries the category name of the first JAVA category to be loaded; S502, searching for the first JAVA category storage address from the category registry according to the category name, according to the storage address from the first JAVA category The storage device obtains the latest version number of the first JAVA category; in order to improve the search speed of the data, in some embodiments of the present application, the content in the category registry may be recorded through the category address hash table. Specifically, the category name of the first JAVA category may be recorded through the primary key of the category address hash table, and the first JAVA category storage address is recorded by the value of the primary key of the category address hash table.

Optionally, the version information of the first JAVA category may also be recorded by using a category version hash table. Specifically, the category name of the first JAVA category is recorded by using a primary key of the category version hash table, and the primary key of the category version hash table is used. The value of the record records the version information of the first JAVA category that was last loaded.

S503. Determine whether the latest version number of the first JAVA category is the same as the last stored version number of the first JAVA category stored locally; S504, the latest version number of the first JAVA category and the last stored locally. When the version number of the first JAVA category is different, the first JAVA category of the latest version is acquired, the loading is performed, and the version number of the first JAVA category is updated in the category version record; otherwise, the version is directly loaded. The first JAVA category.

In order to further ensure the implementation of the loading method shown in FIG. 5, the embodiment of the present application further provides a class library registration method. Referring to FIG. 6, the method includes: S601, obtaining a JAVA category according to the received JAVA class library storage address. a library; 602, traversing the JAVA category library, inserting a new category in the category registry that is not recorded in the JAVA category library into the category registry; the content in the category registry includes a category name, a category The library name and the storage address of the category library.

S603. Traverse the JAVA category library, and update a storage address of the corresponding JAVA category in the registry according to the storage address of each JAVA category recorded in the JAVA category library.

The method provided by the embodiment of the present application realizes the registration of the new category through S602, and ensures the integrity of the JAVA category library. The storage address of each JAVA category can be updated in real time through the S603, and the JAVA category library is guaranteed. The accuracy of the information saved provides a favorable guarantee for the smooth implementation of the method shown in FIG.

FIG. 7 is a code device method according to another embodiment of the present application, in which a programmer writes a JAVA category, and the function of the JAVA category is to print the phrase “hello, world” on a webpage. . The file name for this category is helloworld.class, which is packaged in the JAVA package hello.jar and uploaded to the SVN server.

In the embodiment of the present application, all the categories in the JAVA package of hello.jar and the url of the JAV package corresponding to the SVN server of the hello.jar are recorded in the category registry (ClassTable).

When a program aaaa on a certain server in the JAVA cluster needs to call the category helloworld.class during the execution, the code device method provided by the embodiment of the present application is specifically: S701, when the program aaaa is started, The class loading device located in the server traverses the records in the ClassTable, and records all categories and corresponding SVN URLs into the local class address hash table (SvnUrlMap).

S702. When the program aaaa is executed to call helloworld.class, the category loading device finds the SVN URL of the jar package corresponding to helloworld.class from the SvnUrlMap.

S703. Access the SVN server according to the SVN URL, obtain the hello.jar package corresponding to helloworld.class, and obtain the latest version number of helloworld.class.

For example, at this time, the latest version number of helloworld.class is 10000.

S704: Record the category name of the helloworld.class and the latest version number into the local version hash table (ClassVersionMap), the key of the hash table is “helloworld”, and the value of the primary key is 10000.

S705. Download helloworld.class from the SVN server.

S706, load helloworld.class and run the category.

Suppose that after this, the programmer A modified helloworld.class, and repackaged hello.jar, and then submitted to the SVN server, the SVN server accepted the latest hello.jar, and produced a new version number 10001.

At this time, if aaaa is run again, when it wants to call helloworld.class again, referring to FIG. 8, the loading method provided by the embodiment of the present application is: S801, the loading device in the server where aaaa is located according to "helloworld" "Find the corresponding SVN URL from SvnUrlMap.

Because the information of the category helloworld has been recorded in this time through the method shown in FIG. 7, when the method calls the category again, the SVN URL corresponding to the category can be directly searched from the local SvnUrlMap.

S802. Access the SVN server according to the SVN URL, obtain the latest version number of helloworld.class is 10001, S803, compare the latest version number of helloworld.class with the version number of helloworld.class recorded in the locally stored ClassVersionMap, and judge two Whether they are consistent, if they are consistent, go to step S805, otherwise go to S804.

In the embodiment of the present application, the version number of the locally recorded helloworld.class is 10000, and the latest version number of helloworld.class obtained from the SVN server is 10001, and the latest version number of helloworld.class is found to be better than the local record by comparison. The version number is larger, indicating that helloworld.class is updated.

S804. Download the latest helloworld.class from the SVN server according to the SVN URL.

S805, load helloworld.class, and run.

The method provided by the embodiment of the present application registers each new category in advance. When a category is likely to be called, the storage address of the category is obtained according to the registration information of the category, and the version information of the category is obtained from the storage location of the category through the storage address, and the latest version of the category is obtained through comparison. And load and call. The method provided by the embodiment of the present application does not need to release the latest code to each server in the cluster, and does not need to restart the JAVA application of each server of the cluster, and only needs to update the code in the code storage server, such as the SVN server. Each server in the cluster can automatically load the latest code, which improves the usability of the JAVA cluster system and improves the efficiency of code loading.

For convenience of description, the embodiments of the present application are separately described in terms of functions by various units when describing the device. Of course, the functions of each unit can be implemented in the same software or software and/or hardware in the implementation of the present application.

It will be apparent to those skilled in the art from the above description of the embodiments that the present application can be implemented by means of a software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , optical discs, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods of various embodiments of the present application or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

This application can be used in numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, small computers, Large computers, decentralized computing environments including any of the above systems or devices, and more.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data categories. The present application can also be practiced in a decentralized computing environment in which tasks are performed by remote processing devices that are coupled through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media, including storage devices.

While the present invention has been described by way of example, it will be understood by those skilled in the art The spirit of the application.

101. . . Receiving unit

102. . . Search unit

103. . . Judging unit

104. . . Processing unit

201. . . database

202. . . Code loading device

203. . . server

204. . . SVN server

301. . . First acquisition subunit

302. . . Second acquisition subunit

303. . . First processing subunit

304. . . Second processing subunit

401. . . Acquisition unit

402. . . New unit

403. . . Update unit

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are merely Some of the embodiments described in the present application can also obtain other drawings based on these drawings without departing from the prior art for those skilled in the art.

1 is a schematic structural diagram of an apparatus according to an embodiment of the present application;

2 is a schematic structural diagram of an application scenario of an apparatus provided by an embodiment of the present application according to another embodiment of the present application;

3 is a schematic structural diagram of a unit in an apparatus according to an embodiment of the present application;

4 is a schematic structural diagram of a system according to an embodiment of the present application;

FIG. 5 is a flowchart of a method according to an embodiment of the present disclosure;

6 is a flow chart of another method provided by an embodiment of the present application;

Figure 7 is a flowchart of a method provided by an embodiment of the present application;

FIG. 8 is a flowchart of a method provided by another embodiment of the present application.

101. . . Receiving unit

102. . . Search unit

103. . . Judging unit

104. . . Processing unit

Claims (12)

An apparatus for code loading of a JAVA cluster application system, characterized in that the server located in the JAVA cluster includes: a receiving unit, configured to receive a category loading request sent by a server, where the category loading request carries a category name of the first JAVA category; a search unit, configured to search for a storage address of the entity of the first JAVA category from the category registration information according to the category name, and store from the first JAVA category according to the storage address Obtaining the latest version number of the first JAVA category, wherein the category registration information is recorded through a category registry, the category registration information including a JAVA category name, a name of a jar package to which the JAVA category belongs, and a jar package to which the JAVA category belongs. Corresponding SVN address, the category registry is stored in the database, and the information in the category registry is read by communicating with the database, wherein the category registry is maintained by the category library registration system, and the category library registration system will The new category note in the JAVA category library is recorded to the category registry, which is based on the storage address of each JAVA category recorded in the JAVA category library. The storage address of the corresponding JAVA category in the new registry, the SVN address is a storage address corresponding to the jar package stored on the SVN server, and the SVN server records each update of the JAVA category, the user Each time the JAVA code is modified and the modified JAVA code is submitted to the SVN server through the SVN client software, the SVN server will generate a new version for the modified JAVA code and record the new version. The version number records the JAVA code of each version; the judging unit is configured to judge the latest version number of the first JAVA category Whether it is the same as the last stored version number of the first JAVA category stored locally; and a processing unit for the latest version number of the first JAVA category and the last stored first JAVA category stored locally The version number of the first JAVA category is not loaded from the storage location of the first JAVA category, the first JAVA category is loaded, and the version number of the first JAVA category is updated in the category version record; otherwise, the version is directly loaded. The first JAVA category. The device according to claim 1, wherein the search unit records the content in the category registration information by using a category address hash table. The device of claim 2, wherein the category name of the first JAVA category is recorded by a primary key of the category address hash table, and the first JAVA category storage location is recorded by a value of a primary key of the category address hash table. site. The device of claim 1, wherein the search unit records version information of the first JAVA category through a category version hash table. The device of claim 4, wherein the category name of the first JAVA category is recorded by a primary key of the category version hash table, and the last loaded number is recorded by the value of the primary key of the category version hash table. The version number of a JAVA category. A category library registration system, characterized in that it is used to maintain category registration information, and the system includes: An obtaining unit, configured to obtain a JAVA category library according to the received JAVA category library storage address; a new unit, configured to traverse the JAVA category library, and not included in the category registration information, included in the JAVA category library The new category is inserted into the category registration information; and an update unit is configured to traverse the JAVA category library, and update the storage address of the corresponding JAVA category in the registration information according to the storage address of each JAVA category recorded in the JAVA category library. The category registration information is recorded by the category registry, and the category registration information includes the JAVA category name, the name of the jar package to which the JAVA category belongs, and the SVN address corresponding to the jar package to which the JAVA category belongs, and the category registry is saved. In the database, the information in the category registry is read by communicating with the database, wherein the category registry is maintained by the category library registration system, and the category library registration system records the new category notes in the JAVA category library to the category. The registry, the category library registration system updates the corresponding JAVA category in the registry according to the storage address of each JAVA category recorded in the JAVA category library. The address of the SVN is the storage address corresponding to the jar package stored on the SVN server. The SVN server records each update of the JAVA category, and the user modifies the JAVA code each time and will modify it. After the JAVA code is submitted to the SVN server through the SVN client software, the SVN server will generate a new version for the modified JAVA code, record the new version, and record the JAVA code of each version through the version number. A JAVA cluster application system code loading method, its characteristics The server for the JAVA cluster includes: receiving, by the server, a category loading request sent by the server, the category loading request carrying a category name of the first JAVA category to be loaded; and registering from the category according to the category name Searching for the first JAVA category storage address in the information, and obtaining the latest version number of the first JAVA category from the storage location of the first JAVA category according to the storage address, wherein the category registration information is recorded through the category registry, The category registration information includes the JAVA category name, the name of the jar package to which the JAVA category belongs, and the SVN address corresponding to the jar package to which the JAVA category belongs. The category registry is stored in the database, and the category is read by communicating with the database. The information in the registry, wherein the category registry is maintained by a category library registration system that records new category notes in the JAVA category library to the category registry, which is based on records in the JAVA category library The storage address of each JAVA category updates the storage address of the corresponding JAVA category in the registry, and the SVN address corresponds to the jar package stored on the SVN server. The address is stored, and the SVN server records each update of the JAVA category. Each time the user modifies the JAVA code and submits the modified JAVA code to the SVN server through the SVN client software, the SVN server will The modified JAVA code generates a new version, records the new version, records the JAVA code of each version through the version number; determines the latest version number of the first JAVA category and the last stored version of the local storage Whether the version number of a JAVA category is the same; and the first version that was last loaded in the latest version number and locally stored When the version number of the JAVA category is the same, the first JAVA category of the latest version is obtained, loaded, and the version number of the first JAVA category is updated in the category version record; otherwise, the first JAVA category is directly loaded. The method of claim 7, wherein the content in the category registration information is recorded by a category address hash table. The method of claim 8, wherein the content of the category registration information is recorded by the category address hash table, wherein the category name of the first JAVA category is recorded through the primary key of the category address hash table. The value of the primary key of the category address hash table records the first JAVA category storage address. The method of claim 7, wherein the version information of the first JAVA category is recorded by a category version hash table. The method of claim 10, wherein the version information of the first JAVA category is recorded through a category version hash table, wherein the first JAVA category name is recorded through the primary key of the category version hash table. The value of the primary key of the category version hash table records the version information of the first JAVA category that was last loaded. A class library registration method, comprising: obtaining a JAVA class library according to the received JAVA class library storage address; traversing the JAVA class library, and not including the category registration information, included in the JAVA class library Insert a new category into the category registration information; and Traversing the JAVA category library, updating the storage address of the corresponding JAVA category in the registration information according to the storage address of each JAVA category recorded in the JAVA category library, wherein the category registration information is recorded through the category registry, the category registration The information includes the JAVA category name, the name of the jar package to which the JAVA category belongs, and the SVN address corresponding to the jar package to which the JAVA category belongs. The category registry is stored in the database, and the category registry is read by communicating with the database. The information in the category registry is maintained by the category library registration system, which records the new category notes in the JAVA category library to the category registry, which is based on the records in the JAVA category library. The storage address of the JAVA category updates the storage address of the corresponding JAVA category in the registry, and the SVN address is the storage address corresponding to the jar package stored on the SVN server, and the SVN server is for each JAVA category. The update is recorded, the user changes the JAVA code each time, and the modified JAVA code is submitted to the SVN server through the SVN client software, the SVN server It will produce a new version of JAVA for the modified code, and the new version is recorded through the version number of the record of each version of JAVA code.