CN103259676A - Method and device for fault diagnosis - Google Patents
Method and device for fault diagnosis Download PDFInfo
- Publication number
- CN103259676A CN103259676A CN2013101294065A CN201310129406A CN103259676A CN 103259676 A CN103259676 A CN 103259676A CN 2013101294065 A CN2013101294065 A CN 2013101294065A CN 201310129406 A CN201310129406 A CN 201310129406A CN 103259676 A CN103259676 A CN 103259676A
- Authority
- CN
- China
- Prior art keywords
- destination object
- server
- address
- shooter
- trouble
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and device for fault diagnosis. The method comprises the following steps: obtaining IOR, analyzing the IOR, obtaining corresponding object address information of a target object, executing access to the target object according to the object address information, and obtaining a fault occurrence location according to an access result. The method and device for the fault diagnosis can diagnose fault locations rapidly, and fault diagnosis efficiency is improved.
Description
Technical field
The present invention relates to network technology, relate in particular to a kind of method for diagnosing faults and device.
Background technology
In order to satisfy the interoperability between the object that is positioned at diverse location in the distributed objects environment, prior art provides the system architecture that is used for the object interoperability, (Common Object Request Broker Architecture is called for short: CORBA) such as Common Object Request Broker Architecture.In the CORBA architecture, contacting and the calling of objects services between client and the server, (Object Request Broker is called for short: ORB) carry out by Object Request Broker; And (Interoperable Object Reference is called for short: IOR) announce, with the means of this IOR as identifying object the objects services that server also can provide it by the interoperability object reference.This IOR has encapsulated the required various information of client and server contact, and client sends the objects services call request by these information to ORB, and ORB sends to server with request and handles, and result is returned to client.
The problem that prior art exists is: when client is served at allocating object, if the situation of malloc failure malloc, can't judge the ownership of problem fast, such as, do not know that client goes wrong, or network connectivity problem or server end problem, thereby make that the time of CORBA service disruption is longer, can not in time repair fault, failure diagnosis efficient is low, influences the normal use of client.
Summary of the invention
The invention provides a kind of method for diagnosing faults and device, to improve failure diagnosis efficient.
First aspect provides a kind of method for diagnosing faults, comprising:
When the client-access destination object was failed, trouble-shooter obtained the interoperability object reference IOR of described destination object;
Described trouble-shooter is resolved described IOR, obtains the object address information of described destination object correspondence;
Described trouble-shooter is according to the described destination object of described object address message reference, and determines the fault occurrence positions according to the visit result.
In conjunction with first aspect, in first kind of possible implementation, described trouble-shooter is positioned at the same network segment with the described client of the described destination object failure of visit; The described IOR that obtains destination object comprises: the IOR that obtains described destination object by the Internet.
In conjunction with first kind of first aspect possible implementation, in second kind of possible implementation, described object address information comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, and comprising: described trouble-shooter connects according to described server address and described server; Described trouble-shooter is visited described destination object according to described object address, if visit is normal, determines that then the fault occurrence positions is positioned at described client.
In conjunction with first aspect, in the third possible implementation, the server at described trouble-shooter and described destination object place is positioned at the same network segment; The described IOR that obtains destination object comprises: the IOR that obtains described destination object in the described same network segment.
The third possible implementation in conjunction with first aspect, in the 4th kind of possible implementation, described object address information comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, and comprising: described trouble-shooter connects according to described server address and described server; Described trouble-shooter is visited described destination object according to described object address, if can't visit, determines that then the fault occurrence positions is positioned at described server.
In conjunction with first aspect, in the 5th kind of possible implementation, described object address information comprises: the server address at described destination object place; Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, and comprising: described trouble-shooter connects according to described server address and described server; Described trouble-shooter calls the service interface of described server, if can't call, determines that then the fault occurrence positions is positioned at the service interface of described server.
In conjunction with first aspect, in the 6th kind of possible implementation, after the object address information of described acquisition destination object correspondence, and according to before the described destination object of described object address message reference, also comprise: described trouble-shooter checks the correctness of described object address information, and revises when inspection makes mistake.
In conjunction with first aspect, in the 7th kind of possible implementation, described destination object is the CORBA object.
Second aspect provides a kind of trouble-shooter, comprising:
Information acquisition unit is used for obtaining the interoperability object reference IOR of described destination object when the client-access destination object is failed;
The information analysis unit is used for resolving described IOR, obtains the object address information of destination object correspondence;
Failure diagnosis unit is used for according to the described destination object of described object address message reference, and determines the fault occurrence positions according to the visit result.
In conjunction with second aspect, in first kind of possible implementation, described information acquisition unit, concrete being used for obtained the IOR of described destination object by the Internet when the described client of the described destination object failure of described device and visit is positioned at the same network segment.
In conjunction with first kind of second aspect possible implementation, in second kind of possible implementation, the described object address information that described information analysis unit obtains comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described failure diagnosis unit comprises: connect and set up subelement, be used for connecting according to described server address and described server; The object accesses subelement is used for visiting described destination object according to described object address; Judgment sub-unit is used in described visit subelement visit just often determining that the fault occurrence positions is positioned at described client as a result.
In conjunction with second kind of second aspect possible implementation, in the third possible implementation, described information acquisition unit when the concrete server that is used at described device and described destination object place is positioned at the same network segment, is obtained the IOR of described destination object in the described same network segment.
The third possible implementation in conjunction with second aspect, in the 4th kind of possible implementation, described judgment sub-unit as a result, when also being positioned at the same network segment for the server at described device and described destination object place, if described visit subelement can't be visited, determine that then the fault occurrence positions is positioned at described server.
In conjunction with the third possible implementation of second aspect, in the 5th kind of possible implementation, described failure diagnosis unit also comprises: the interface interchange subelement, for the service interface that calls described server; Described judgment sub-unit as a result also is used for when described interface interchange subelement can't call, and determines that then the fault occurrence positions is positioned at the service interface of described server.
In conjunction with second aspect, in the 6th kind of possible implementation, also comprise: the information check unit, the correctness that is used for object address information that described information analysis unit is obtained checks, and revises when inspection makes mistake.
The technique effect of method for diagnosing faults provided by the invention and device is: by obtaining IOR and resolving the object address information that obtains, according to this object address message reference destination object, can obtain the fault occurrence positions according to the visit result, this method provides the mode of failure diagnosis, and this diagnostic mode ratio faster, can diagnose the position of being out of order faster, thereby improve failure diagnosis efficient.
Description of drawings
Fig. 1 uses schematic diagram one for the CORBA of method for diagnosing faults embodiment of the present invention;
Fig. 2 uses schematic diagram two for the CORBA of method for diagnosing faults embodiment of the present invention;
Fig. 3 is the schematic flow sheet of method for diagnosing faults one embodiment of the present invention;
Fig. 4 is the far-end diagnosis schematic diagram of another embodiment of method for diagnosing faults of the present invention;
Fig. 5 is the near-end diagnosis schematic diagram of the another embodiment of method for diagnosing faults of the present invention;
Fig. 6 is the structural representation of trouble-shooter one embodiment of the present invention;
Fig. 7 is the structural representation of another embodiment of trouble-shooter of the present invention;
Fig. 8 is the structural representation of the another embodiment of trouble-shooter of the present invention;
Fig. 9 is the structural representation of the another embodiment of trouble-shooter of the present invention;
Figure 10 is the entity structure diagram of trouble-shooter embodiment of the present invention.
Embodiment
The method for diagnosing faults that the embodiment of the invention provides goes for the object reference of multiple system type, and for example CORBA, JACORB etc. are so long as all be suitable for based on the system of IOR.In the following embodiments, will be example with CORBA, illustrate how to implement this method for diagnosing faults.For feasible clearer for the explanation of this method, at first provide the architectural framework of CORBA: Fig. 1 to use schematic diagram one for the CORBA of method for diagnosing faults embodiment of the present invention, Fig. 2 uses schematic diagram two for the CORBA of method for diagnosing faults embodiment of the present invention.
Referring to illustrated in figures 1 and 2, be connected (described server is among the CORBA agency in Fig. 1) by Internet between client (Client) and the server (Server), store the service that it can provide on the server, each service is represented with a CORBA object, is called Servant; Also there is portable object adapter (the Portable Object Adapter that generates when starting on the server, be called for short: POA), this POA can generate the interoperability object reference IOR of corresponding each object, server is when externally announcing the service that oneself can provide, it is the mode by output IOR, this IOR is binary character string, and the example of an optional IOR is as follows:
IOR:010000003100000049444c3a6d746e6d2e746d666f72756d2e6f72672f6e6d7353657373696f6e2f4e6d7353657373696f6e5f493a312e300000000001000000000000006400000001010200180000006c33303139322e6368696e612e6875617765692e636f6d009f0a030014000000004f4f01c60be628ff000000504f41fec1e2955101000000010000001c00000000000000000100010000000100010020000101090000000100010100
Concrete, this IOR is for the described CORBA object of sign, if the service that client wants certain the CORBA object on the invoking server to provide need be called according to the information that provides among this IOR, come to send call request to server according to the described information that provides.Encapsulated among this IOR and sent the needed content of described call request, for example, the IP address of the host-host protocol of use, object place server, port numbers etc.For example, the composition structure of a kind of IOR of following example, following structure are the contents that obtains after the IOR of above-mentioned binary-coded character string format is resolved:
Composition referring to above-mentioned IOR, it mainly comprises three parts: warehouse ID, endpoint information and object key, described endpoint information refers to for example Host, Port, described object key refers to for example Object key (URL), Object key (hex), and this is two kinds of different expression waies of object key.Wherein, described endpoint information is used for the server address at indicated object place, and described object key is used for indicated object in the object address of server, such as removing to seek object by the POA on the server.
In the CORBA system, when user end to server sends call request, carry out by ORB; Be that client can send to ORB with call request earlier, ORB is passed to server with this request, and server is transferred to POA with request, and POA passes to CORBA object Servant to request again; Servant returns to client with the result by ORB after its service that provides is provided.Wherein, ORB, POA can be arranged on CORBA agency shown in Figure 1, act on behalf of side at CORBA and also be provided with other service equipments, for example Naming Service, Notify Service etc., owing to be routine techniques, so no longer shown in Fig. 1, the IOR that server is announced can be placed on Naming Service, client can be obtained the IOR of its destination object that will visit from Naming Service.
The method for diagnosing faults that provides of the embodiment of the invention in the time of can being used for the object when the client call service device, takes place under the situation of malloc failure malloc, how to diagnose the position of the generation of being out of order, and for example is that client goes wrong, or server problem etc.For this reason, the embodiment of the invention provides a kind of trouble-shooter, uses this device to carry out described method for diagnosing faults.
Embodiment one
Fig. 3 is the schematic flow sheet of method for diagnosing faults one embodiment of the present invention, and this method is to be carried out by trouble-shooter, as shown in Figure 3, can comprise:
301, trouble-shooter obtains the interoperability object reference IOR of destination object;
Wherein, when the client-access destination object was failed, trouble-shooter can obtain the interoperability object reference IOR of this destination object.
For example, trouble-shooter can obtain this IOR by being positioned at the Naming Service that CORBA acts on behalf of side.Wherein, described destination object is that client is wanted the object Servant that visits; This destination object is stored in server, can be that (Interface description language, be called for short: IDL) definition realizes server according to interface description language.
302, trouble-shooter is resolved described IOR, obtains the object address information of destination object correspondence;
Described object address information, can be in conjunction with referring to recited above IOR after binary IOR parsing being formed structure, can comprise: the server address at destination object place (for example Host, Port) and destination object are in the object address (for example Object key) of server.
303, trouble-shooter is according to the described destination object of described object address message reference, and determines the fault occurrence positions according to the visit result.
Wherein, described access destination object comprises polytype visit; For example, destination object is stored on the server, then comprises the visit to this server, can judge whether the service interface (corba interface) of server is available according to visit result (whether can visit), if such as visiting, show that then the corba interface of server is normal;
Perhaps, can also comprise the visit to the destination object on the server, i.e. the service of the such direct invocation target object of similar client (CORBA service) can judge whether server exists fault according to the visit result.For example, when trouble-shooter and server are placed on the same network segment, if can not visit the CORBA service, then show the server end fault.
Described to determine that the mode of fault occurrence positions can have multiple according to the visit result, will describe several optional diagnosis schemes in follow-up embodiment.The embodiment of the invention can quick diagnosis go out to take place the location of fault place by method for diagnosing faults is provided, and improves diagnosis efficiency.
Embodiment two
Present embodiment provides a kind of far-end diagnostic mode, this far-end diagnosis refers to trouble-shooter is placed on and the same network segment of client, referring to Fig. 1, when with trouble-shooter and the same network segment of client, this device if the Connection Service device also need through the Internet in the Internet and router.
Fig. 4 is the far-end diagnosis schematic diagram of another embodiment of method for diagnosing faults of the present invention, as shown in Figure 4, trouble-shooter and client are positioned at the same network segment, this trouble-shooter for example can be certain diagnostic software, this software be present in certain with the separate machine of client on, perhaps this software also can be to be located immediately on the client; Described client be before the client of access destination object failure, for example this client is in the service of wanting before the invocation target object, but malloc failure malloc, so at the network segment same with it this trouble-shooter is set.
Wherein, trouble-shooter obtains described IOR by the Internet, for example is by Internet, router, and the Naming Service that acts on behalf of the same network segment from CORBA obtains IOR; And this IOR resolved, analysis mode can use flexibly, and such as the dior command analysis that can use Jacorb, the usage of dior is as follows:
Usage:dior[-i?ior_str|-f?filename]
After resolving IOR, can obtain the object address information of destination object correspondence, this address information for example comprises: the server address at destination object place (such as Host, Port) and be used for the described destination object of expression in the object address (such as object key) of server address.
Trouble-shooter will at first connect according to above-mentioned information and server after resolving the above-mentioned object address information of IOR acquisition, could begin diagnostic work after connecting.For example, can carry ORB assembly etc. by jacorb or java JDK, create and being connected of server according to above-mentioned server address, such as passing through the mode shown in Fig. 4, still connect by ORB and server.
Optionally, after obtaining above-mentioned object address information, trouble-shooter can also check the correctness of object address information, and revises when inspection makes mistake.Correctness described here checks, can be the inspection about object address message form and form, for example, resolving the server ip address that obtains is 10.4070.86, just can find format error by checking, lack a decimal point, it is modified to 10.40.70.86.Can also be by telnet port numbers available inspection the whether.
Optionally, after connecting with server, trouble-shooter can carry out the diagnosis of the service interface of server earlier, and this service interface for example is the corba interface of server.Trouble-shooter calls the corba interface that some standardized interfaces come invoking server, the availability of diagnosis corba interface; This standardized interface for example is ping, get Supported Managers etc.And judge according to the result of interface interchange whether interface exists fault.
Be exemplified below, if the IP address of standard interface ping server, the result can't call, and can determine that then there is fault in the corba interface of server; If the IP address of standard interface ping server, the result can normally return, and illustrates that then the corba interface of server can be used.
Optionally, after to the diagnosis of the corba interface of server, whether trouble-shooter can also continue CORBA service that the destination object on the diagnosis server provides can normal call; Specifically be to resolve the object address Object key (URL) that the back obtains according to IOR, remove to visit this object, if trouble-shooter can normally be visited, and client can't be visited, can determine that then there is fault in client, be that the fault occurrence positions is positioned at this client, such as the configuration or the connected mode that are client problem arranged; And if trouble-shooter can not normally be visited, then may be that the network connection of Internet has problem or server end that problem is arranged, can comprehensively determine further combined with the near-end diagnosis of back embodiment this moment.
Embodiment three
Present embodiment provides a kind of near-end diagnostic mode, this near-end diagnosis refers to trouble-shooter is placed on and the same network segment of server, referring to Fig. 1, when with trouble-shooter and the same network segment of server, this device is if the Connection Service device, do not need directly in the same network segment, to obtain IOR through the Internet in the Internet and router.
Fig. 5 is the near-end diagnosis schematic diagram of the another embodiment of method for diagnosing faults of the present invention, as shown in Figure 5, the server at trouble-shooter and destination object place is positioned at the same network segment, this trouble-shooter for example can be certain diagnostic software, this software be present in certain with the separate machine of server on, perhaps this software also can be to be located immediately on the server, perhaps is positioned at the CORBA agency.
Wherein, trouble-shooter obtains described IOR, for example is that the Naming Service from the same network segment obtains IOR; And this IOR resolved, analysis mode can use flexibly.After resolving IOR, can obtain the object address information of destination object correspondence, this address information for example comprises: the server address at destination object place (such as Host, Port) and described destination object are in the object address (such as object key) of server.
Similar with the far-end diagnostic mode, trouble-shooter will at first connect according to above-mentioned information and server after resolving the above-mentioned object address information of IOR acquisition, could begin diagnostic work after connecting.For example, can carry ORB assembly etc. by jacorb or java JDK, create and being connected of server according to above-mentioned server address, such as still connecting by ORB and server.
Optionally, trouble-shooter also can check the correctness of object address information, and revises when inspection makes mistake; The availability of the corba interface of all right diagnosis server.These can no longer describe in detail referring to the far-end diagnostic mode.
When whether CORBA that the destination object of the trouble-shooter of present embodiment on diagnosis server provides service can normal call, diagnostic mode was diagnosed different with far-end.Concrete, if trouble-shooter can't the access destination object, can determine that then there is fault in server, namely the fault occurrence positions is positioned at this server; And if trouble-shooter can normally be visited, the CORBA service energy normal call of server then is described, server end is no problem, the network connection that so just may be Internet has problem or client that problem is arranged, and can comprehensively determine in conjunction with the far-end diagnosis of front embodiment this moment.
From above-mentioned diagnosis as can be seen, when the trouble-shooter in the far-end diagnosis can be normal during the access destination object, can determine that client breaks down; When the trouble-shooter in the near-end diagnosis normally during the access destination object, can determine that server breaks down.And if normal normal access destination object when (showing that fault is in network or client) of the trouble-shooter in access destination object (showing that fault is at network or server) and the near-end diagnosis of the trouble-shooter in the far-end diagnosis, get the common factor of two judged results, can determine that fault occurs in network, for example be the network connection fault.
Embodiment four
Fig. 6 is the structural representation of trouble-shooter one embodiment of the present invention, and this device can be carried out the method for any embodiment of the present invention, and as shown in Figure 6, this device can comprise: information acquisition unit 61, information analysis unit 62 and failure diagnosis unit 63; Wherein,
Further, information acquisition unit 61, concrete being used for obtained the IOR of described destination object by the Internet when the client of the described destination object failure of described device and visit is positioned at the same network segment.
Fig. 7 is the structural representation of another embodiment of trouble-shooter of the present invention, and as shown in Figure 7, on the basis of Fig. 6 structure, failure diagnosis unit 63 can comprise: connect and set up subelement 631, object accesses subelement 632 and judgment sub-unit 633 as a result; Wherein,
The described object address information that described information analysis unit obtains comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of server address;
Connect and set up subelement 631, be used for connecting according to described server address and described server;
Object accesses subelement 632 is used for visiting described destination object according to described object address;
Further, information acquisition unit 61 when the concrete server that is used at described device and described destination object place is positioned at the same network segment, is obtained the IOR of described destination object in the described same network segment.
Further, described judgment sub-unit as a result 633 when also being positioned at the same network segment for the server at described device and described destination object place, if described visit subelement can't be visited, determines that then there is fault in described server.
Fig. 8 is the structural representation of the another embodiment of trouble-shooter of the present invention, and as shown in Figure 8, on the basis of Fig. 7 structure, failure diagnosis unit 63 can also comprise: interface interchange subelement 634;
Described judgment sub-unit as a result 633 also is used for when described interface interchange subelement can't call, and determines that then there is fault in the service interface of described server.
Fig. 9 is the structural representation of the another embodiment of trouble-shooter of the present invention, as shown in Figure 9, on the basis of structure shown in Figure 6, this device can also comprise: information check unit 64, correctness for the object address information that described information analysis unit is obtained checks, and revises when inspection makes mistake.Certainly this information check unit 64 also is applicable at Fig. 7 or Fig. 8 increases, and no longer illustrates.
By the trouble-shooter that adopts the embodiment of the invention to provide, carry out the fault diagnosis method method of any embodiment of the present invention, diagnosis efficiency is improved at the place, position that can quick diagnosis goes out to break down.
Embodiment five
Figure 10 is the entity structure diagram of trouble-shooter embodiment of the present invention, and this device can be carried out the method for any embodiment of the present invention, and as shown in figure 10, this device can comprise: processor 1001, memory 1002, bus 1003 and communication interface 1004.Connect by bus 1003 between processor 1001 and memory 1002 and the communication interface 1004 and finish mutual communication.Processor 1001 may be monokaryon or multinuclear CPU (Central Processing Unit, be called for short: CPU), perhaps be specific integrated circuit (Application Specific Integrated Circuit, be called for short: ASIC), perhaps for being configured to implement one or more integrated circuits of the embodiment of the invention.Memory 1002 can be the high-speed RAM memory, also can be nonvolatile memory (non-volatile memory), for example at least one magnetic disc store.
Optionally, memory 1002 also is used for the described IOR of storage and object address information.
Further, processor 1001 also by computer instructions, when being positioned at the same network segment with the client in the described destination object failure of described device and visit, obtains the IOR of described destination object by communication interface 1004.
Further, the described object address information that obtains of processor 1001 comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of server address; Processor 1001 when carrying out according to the described destination object step of described object address message reference, specifically is to connect according to described server address and described server, correspondingly, processor 1001 visit just often definite described client have fault.
One of ordinary skill in the art will appreciate that: all or part of step that realizes above-mentioned each method embodiment can be finished by the relevant hardware of program command.Aforesaid program can be stored in the computer read/write memory medium.This program is carried out the step that comprises above-mentioned each method embodiment when carrying out; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
It should be noted that at last: above each embodiment is not intended to limit only in order to technical scheme of the present invention to be described; Although the present invention has been described in detail with reference to aforementioned each embodiment, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment puts down in writing, and perhaps some or all of technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the scope of various embodiments of the present invention technical scheme.
Claims (15)
1. a method for diagnosing faults is characterized in that, comprising:
When the client-access destination object was failed, trouble-shooter obtained the interoperability object reference IOR of described destination object;
Described trouble-shooter is resolved described IOR, obtains the object address information of described destination object correspondence;
Described trouble-shooter is according to the described destination object of described object address message reference, and determines the fault occurrence positions according to the visit result.
2. method according to claim 1 is characterized in that, described trouble-shooter is positioned at the same network segment with the described client of the described destination object failure of visit;
The described IOR that obtains destination object comprises: the IOR that obtains described destination object by the Internet.
3. method according to claim 2 is characterized in that, described object address information comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, comprising:
Described trouble-shooter connects according to described server address and described server;
Described trouble-shooter is visited described destination object according to described object address, if visit is normal, determines that then the fault occurrence positions is positioned at described client.
4. method according to claim 1 is characterized in that, the server at described trouble-shooter and described destination object place is positioned at the same network segment;
The described IOR that obtains destination object comprises: the IOR that obtains described destination object in the described same network segment.
5. method according to claim 4 is characterized in that, described object address information comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, comprising:
Described trouble-shooter connects according to described server address and described server;
Described trouble-shooter is visited described destination object according to described object address, if can't visit, determines that then the fault occurrence positions is positioned at described server.
6. method according to claim 1 is characterized in that, described object address information comprises: the server address at described destination object place;
Described trouble-shooter is according to the described destination object of described object address message reference, and obtains the fault occurrence positions according to the visit result, comprising:
Described trouble-shooter connects according to described server address and described server;
Described trouble-shooter calls the service interface of described server, if can't call, determines that then the fault occurrence positions is positioned at the service interface of described server.
7. method according to claim 1 is characterized in that, after the object address information of described acquisition destination object correspondence, and according to before the described destination object of described object address message reference, also comprises:
Described trouble-shooter checks the correctness of described object address information, and revises when inspection makes mistake.
8. diagnostic method according to claim 1 is characterized in that, described destination object is the CORBA object.
9. a trouble-shooter is characterized in that, comprising:
Information acquisition unit is used for obtaining the interoperability object reference IOR of described destination object when the client-access destination object is failed;
The information analysis unit is used for resolving described IOR, obtains the object address information of destination object correspondence;
Failure diagnosis unit is used for according to the described destination object of described object address message reference, and determines the fault occurrence positions according to the visit result.
10. device according to claim 9 is characterized in that,
Described information acquisition unit, concrete being used for obtained the IOR of described destination object by the Internet when the described client of the described destination object failure of described device and visit is positioned at the same network segment.
11. device according to claim 10 is characterized in that,
The described object address information that described information analysis unit obtains comprises: the server address at described destination object place and be used for the described destination object of expression in the object address of described server address;
Described failure diagnosis unit comprises:
Connect and set up subelement, be used for connecting according to described server address and described server;
The object accesses subelement is used for visiting described destination object according to described object address;
Judgment sub-unit is used in described visit subelement visit just often determining that the fault occurrence positions is positioned at described client as a result.
12. device according to claim 11 is characterized in that,
Described information acquisition unit when the concrete server that is used at described device and described destination object place is positioned at the same network segment, is obtained the IOR of described destination object in the described same network segment.
13. device according to claim 12 is characterized in that,
Described judgment sub-unit as a result when also being positioned at the same network segment for the server at described device and described destination object place, if described visit subelement can't be visited, determines that then the fault occurrence positions is positioned at described server.
14. device according to claim 12 is characterized in that, described failure diagnosis unit also comprises:
The interface interchange subelement is for the service interface that calls described server;
Described judgment sub-unit as a result also is used for when described interface interchange subelement can't call, and determines that then the fault occurrence positions is positioned at the service interface of described server.
15. device according to claim 9 is characterized in that, also comprises:
The information check unit, the correctness that is used for object address information that described information analysis unit is obtained checks, and revises when inspection makes mistake.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013101294065A CN103259676A (en) | 2013-04-15 | 2013-04-15 | Method and device for fault diagnosis |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013101294065A CN103259676A (en) | 2013-04-15 | 2013-04-15 | Method and device for fault diagnosis |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103259676A true CN103259676A (en) | 2013-08-21 |
Family
ID=48963393
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2013101294065A Pending CN103259676A (en) | 2013-04-15 | 2013-04-15 | Method and device for fault diagnosis |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103259676A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099830A (en) * | 2015-08-28 | 2015-11-25 | 广东小天才科技有限公司 | Method for obtaining location failure reason, mobile terminal and server |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028817A1 (en) * | 2001-08-06 | 2003-02-06 | Shigeru Suzuyama | Method and device for notifying server failure recovery |
| CN1825813A (en) * | 2005-02-25 | 2006-08-30 | 中兴通讯股份有限公司 | Method of access network element managing system for mobile communication service managing system |
| CN101005399A (en) * | 2006-01-16 | 2007-07-25 | 上海贝尔阿尔卡特股份有限公司 | Network device managing method, network device and network managing system |
| JP2011048577A (en) * | 2009-08-26 | 2011-03-10 | Hitachi Kokusai Electric Inc | Failure monitoring system |
| CN102694880A (en) * | 2012-06-07 | 2012-09-26 | 华为技术有限公司 | Method, device and system for acquiring outer network internet protocol (IP) address of remote object |
| CN102932194A (en) * | 2011-08-09 | 2013-02-13 | 中国银行股份有限公司 | Bayes method-based Internet application service monitoring system and method |
-
2013
- 2013-04-15 CN CN2013101294065A patent/CN103259676A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028817A1 (en) * | 2001-08-06 | 2003-02-06 | Shigeru Suzuyama | Method and device for notifying server failure recovery |
| CN1825813A (en) * | 2005-02-25 | 2006-08-30 | 中兴通讯股份有限公司 | Method of access network element managing system for mobile communication service managing system |
| CN101005399A (en) * | 2006-01-16 | 2007-07-25 | 上海贝尔阿尔卡特股份有限公司 | Network device managing method, network device and network managing system |
| JP2011048577A (en) * | 2009-08-26 | 2011-03-10 | Hitachi Kokusai Electric Inc | Failure monitoring system |
| CN102932194A (en) * | 2011-08-09 | 2013-02-13 | 中国银行股份有限公司 | Bayes method-based Internet application service monitoring system and method |
| CN102694880A (en) * | 2012-06-07 | 2012-09-26 | 华为技术有限公司 | Method, device and system for acquiring outer network internet protocol (IP) address of remote object |
Non-Patent Citations (1)
| Title |
|---|
| 核子可乐: "Linux服务器故障排查实用指南", 《HTTP://OS.51CTO.COM/ART/201303/386237_ALL.HTM》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099830A (en) * | 2015-08-28 | 2015-11-25 | 广东小天才科技有限公司 | Method for obtaining location failure reason, mobile terminal and server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103281248B (en) | The discover method of network topology, device and system | |
| TWI282228B (en) | Method and apparatus for autonomic failover | |
| US9723110B2 (en) | System and method for supporting a proxy model for across-domain messaging in a transactional middleware machine environment | |
| CN111917846A (en) | Kafka cluster switching method, device and system, electronic equipment and readable storage medium | |
| JP2001188765A (en) | Technique for referring to fault information showing plural related fault under distributed computing environment | |
| US20090007152A1 (en) | Management of external hardware appliances in a distributed operating system | |
| CN113890879B (en) | Load balancing method and device for data access, computer equipment and medium | |
| US20070219673A1 (en) | Master chassis automatic selection system and method | |
| US8010684B1 (en) | Redirection gateway | |
| CN108089972B (en) | Interface test method and device | |
| CN106603330A (en) | Cloud platform virtual machine connection state checking method | |
| CN113992382A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN112751724B (en) | Method and device for detecting link state | |
| US7724659B2 (en) | Network-based autodiscovery system for MAC forwarding dispatcher | |
| CN103259676A (en) | Method and device for fault diagnosis | |
| EP4031967A1 (en) | Efficiently mapping a distributed resource to a virtual network | |
| CN106161339A (en) | Obtain the method and device of IP access relation | |
| CN110855782B (en) | Service calling system, method, electronic equipment and readable storage medium | |
| CN114629831A (en) | Network card performance test method, device, equipment and storage medium | |
| CN101997704A (en) | Method, device and network management server for realizing element location link state polling | |
| JP2020057908A (en) | Communication failure analysis device, system, method, and program | |
| JP2009530707A (en) | Command line pipelining | |
| JP5047072B2 (en) | Data transfer system, transfer device, monitoring device, transfer program, and monitoring program | |
| WO2017124726A1 (en) | Method, apparatus and system for generating northbound file | |
| CN112286738B (en) | Method, system, equipment and readable storage medium for accessing database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130821 |