JP2019125321A - Communication log recording apparatus, communication log recording method, and communication log recording program - Google Patents

Abstract

To provide a communication log recording apparatus which can restrain communication log saving input/output operations from giving adverse effects on other operations when communication logs are buffered to main memory and then saved to a storage such as an HDD.SOLUTION: A communication recording apparatus 10 comprises: a log collection unit 11; a log save unit 12; a log storage unit 13; a communication counter 14; a log temporary storage unit 15; a reception request storage unit 16; a communication processing unit 21; and a communication wait unit 22. The log collection unit, when executing a communication requested by an application 17 and accepting a reception request, obtains an order from the communication counter to begin generating and receiving a log ID indicating the issue order of the reception request, collects a communication log including the log ID and read reception data, and temporarily stores the communication log in the log temporary storage unit which is faster than the log storage means. The log storage unit, during a communication wait time, reads the communication log from the log temporary storage unit and stores the read communication log in the log storage unit. Communication logs are stored in the log storage unit in succession.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a communication log recording apparatus, a communication log recording method, and a communication log recording program, and more particularly to an apparatus for efficiently recording a communication log including an order of reception requests issued by an application and reception data.

  The communication log including the order of the reception request issued by the application and the reception data is useful data, and is suitable for use in, for example, a data record replay method.

  Program debugging needs to reproduce the state of the problem. A program that communicates between processes to proceed with processing, such as a message passing type / distributed parallel program, communicates between processes to proceed with processing, and therefore communication results are required to reproduce the state. One of the solutions to this problem is a data recording type replay method (Non-Patent Document 1). This records the result of communication performed by the process to be debugged, and at the time of debugging (replay), refers to the previously recorded communication result instead of communication. As a result, actual communication is not necessary, and debugging can be performed only by the process to be debugged.

  Patent Document 1 discloses a method of reproducing execution of a parallel program. In this method, a record in which a parallel program running in monitor mode accesses shared data in the main storage is written to a system history tape stored in the main storage. The method reproduces the execution of the parallel program in the replay mode, using the records written to the system history tape.

  Patent Document 2 buffers communication logs regarded as having continuity in a primary storage area, and when the buffering period expires, stores communication logs stored in the primary storage area in a secondary storage area. Discloses an information processing apparatus.

Japanese Patent Application Laid-Open No. 03-240137 JP, 2011-060030, A

Parallel Program Debugging by Data Reproduction The Journal of Information Processing Society of Japan: Computing System, Vol. 46, No. SIG 12 (ACS11), pp. 214-224, August 2005.

  The communication log used in the data recording type re-execution method of the program accompanied with data reception is characterized in that the amount of data is large since it includes the received data. Such many communication logs can not be kept on the main memory as disclosed in Patent Document 1. Volatility can be a problem.

  On the other hand, as disclosed in Patent Document 2, when the communication log is buffered in the primary storage area such as the main storage and the communication log is stored in the secondary storage area such as a hard disk later, the communication log may be stored. Input and output may adversely affect other processes. That is, when another process waits for the end of input / output of the communication log, this input / output delays the execution of the other process. Even when communication log input / output and the other processing are executed in parallel by asynchronous input / output etc., this input / output adversely affects the other processing environment as follows.

  Problem (a) Even if the program to be reproduced does not use asynchronous I / O, special hardware such as a DMA (Direct Memory Access) engine is required.

  Problem (b) A mechanism and resources for process threads of asynchronous I / O processing are required.

Problem (c) A central processing unit (CPU) core available to a program is reduced because of asynchronous input / output processing.
Problem (d) If the process thread of asynchronous I / O processing and the program share the CPU core, context switch overhead is incurred. In addition, when the program being calculated and asynchronous input / output processing are switched, the CPU core utilization of the calculation decreases. The present invention buffers the communication log in the main storage etc. It is an object of the present invention to provide a communication log recording device and the like which can suppress the influence of input / output at the time of storing again on other processing when storing the data in the memory.

  A communication log recording device according to one embodiment of the present invention is a log storage means, a log temporary storage means faster than the log storage means, and a log ID indicating the issuance order of the reception request when receiving the reception request. Log collection means for starting generation and reception and storing log information including the log ID and the received data read at the end of the reception in the temporary log storage means; requested transmission or the reception is started And log storage means for storing again the log information stored in the temporary log storage means in the log storage means.

  In the communication log recording method according to one embodiment of the present invention, when a reception request is received, generation and reception of a log ID indicating an issuance order of the reception request is performed, and reading of the log ID is performed at the end of the reception. The log information including the received data and the log information stored in the temporary log storage means faster than the log storage means, and after the requested transmission or the reception is started, the log information stored in the temporary log storage means Are stored in the log storage means.

  A communication log recording program according to one embodiment of the present invention receives a reception request from a computer including a log storage unit and a log temporary storage unit faster than the log storage unit, in the order of issuance of the reception request. A log collection process for storing log information including the log ID and the received data read at the end of the reception in the log temporary storage means, and generation of the log ID indicating the start and reception of the requested log or After the reception is started, a log storage process is performed to store the log information stored in the temporary log storage means in the log storage means.

  In the communication log recording apparatus and the like according to the present invention, when the communication log is buffered in the main storage etc. and the communication log is later stored in the hard disk etc., the input / output for re-storage is other Influence on the treatment of

FIG. 1 is a diagram showing the configuration of a communication log recording device 10 according to the first embodiment. FIG. 2 is a diagram showing the data structure of the log temporary storage unit 15 and the communication log stored in the log storage unit 13. FIG. 3 is a view showing a data structure of a table stored in the reception request storage unit 16. FIG. 4 is a diagram showing the configuration of the computer device 60. As shown in FIG. FIG. 5 is a flowchart showing the operation of the log collection unit 11 when communication is requested. FIG. 6 is a flow chart showing the operation of the log collection unit 11 when receiving a termination waiting request for non-blocking communication. FIG. 7 is a flowchart showing the operation of the log storage unit 12. FIG. 8 is a diagram showing a difference between execution times of the case where the communication log of the communication is stored immediately after the end of communication in the timeline (A) and the case of the communication log recording device 10 (B). FIG. 9 is a diagram showing the configuration of the temporary log storage unit 15 in the second embodiment. FIG. 10 is a flowchart showing the operation of the log storage unit 12 according to the second embodiment. FIG. 11 is a diagram showing the effect of the communication log recording device 10 according to the present embodiment in the timeline. FIG. 12 is a diagram showing the configuration of the communication log recording device 10 according to the third embodiment. FIG. 13 is a diagram showing the configuration of the communication log recording device 10 according to the fourth embodiment.

First Embodiment
<Overview>
The communication log recording device 10 according to the present embodiment divides the recording of the communication log into two phases of log collection and log storage. In the log extraction phase, the communication log recording device 10 extracts a communication log and temporarily records the communication log in a high-speed recording medium, for example, a temporary log storage unit 15 such as a semiconductor memory. In the subsequent log storage phase, the communication log recording device 10 moves the communication log from the temporary log storage unit 15 to the log storage unit 13 such as an HDD (Hard Disk Drive) during the communication waiting time.

<Configuration>
FIG. 1 is a diagram showing the configuration of the communication log recording device 10 according to the present embodiment. The communication log recording device 10 includes a log collection unit 11, a log storage unit 12, a log storage unit 13, a communication counter 14, a log temporary storage unit 15, a reception request storage unit 16, a communication processing unit 21, and a communication waiting unit 22. Prepare. Furthermore, the communication log recording device 10 is provided with an application 17 that is a subject that requests communication. This subject may be a program or hardware such as an image processing processor.

  The log collecting unit 11 executes the above-described log collecting phase. That is, the log collecting unit 11 executes the communication requested by the application 17 to collect a communication log and temporarily record the communication log in the temporary log storage unit 15. The log storage unit 12 executes the above-described log collection phase. That is, the log storage unit 12 reads the communication log from the temporary log storage unit 15 during communication waiting time, and stores the communication log in the log storage unit 13 again. The communication log is accumulated in the log storage unit 13.

  The communication counter 14 is a counter that records the order of communication requested by the application 17. The initial value is one. When the log collecting unit 11 receives a request for communication from the application 17, the log collecting unit 11 takes an order from this to generate a log ID (Identification), and increases the value of the communication counter 14 by one.

  The communication processing unit 21 starts communication, and the communication waiting unit 22 waits for the end of communication. The communication referred to here is, for example, inter-process communication, but may be input / output to a disk device or communication with a remote device via a communication network. The reception request storage unit 16 stores a table for obtaining the log ID of the ended communication when non-blocking type, ie, asynchronous type communication is performed.

  FIG. 2 is a diagram showing the data structure of the log temporary storage unit 15 and the communication log stored in the log storage unit 13. The communication log is acquired each time the application 17 requests communication, and stored in one row of the table in FIG. The communication log includes each data item of log ID, communication procedure, execution result, received data, and end flag.

  The log ID indicates the order of communication requested by the application 17. The log ID may include other information, such as an identifier of the application 17 or an identifier of a process. The received data represents the content of the data received in the request. The log ID can be used, for example, to output correct reception data in response to a communication request when the application 17 plays back. That is, if the communication request issued to the n (n is an integer) communication request is a reception request, the system executing the reproduction outputs the reception data of the communication log having the log ID indicating the n th to the application 17 good.

  The communication procedure indicates the type of the request. The communication procedure indicates the distinction between reception / transmission and the distinction between synchronous communication / asynchronous communication. Note that synchronous input / output / asynchronous input / output may be referred to as blocking / non-blocking. The execution result indicates whether the communication has ended normally.

  The end flag has only the communication log in the temporary log storage unit 15, and indicates whether the reception / transmission of the communication request has ended. The end flag has an initial value of 0 and indicates that communication is in progress, and becomes 1 when communication is completed. The log storage unit 12 stores the communication log of the communication request for which reception / transmission has been completed from the temporary log storage unit 15 back to the log storage unit 13. When storing the communication log from the log temporary storage unit 15 into the log storage unit 13 again, the log storage unit 12 removes the end flag.

  Note that the communication log may not include the communication procedure or the execution result if it is not necessary at the time of replaying or the like. For example, when the communication result is always normal, a replay is performed. In addition, the communication log may be acquired only for the reception if the reproduction result is not considered at the time of the re-execution, for example, if the reproduction is always performed normally.

  FIG. 3 is a view showing a data structure of a table stored in the reception request storage unit 16. This table stores the association between the reception request ID and the log ID for the nonblocking communication request being executed. The reception request ID is an identifier of the communication request issued by the application 17. The reception request ID may be any information as long as it can identify the nonblocking communication in progress. The reception request ID is, for example, an address of a control information case variable for managing non-blocking communication in progress or a subscript variable value of an array element.

  Here, the log collection unit 11, the log storage unit 12, the communication processing unit 21, and the communication waiting unit 22 of the communication log recording device 10 are configured by a logic circuit or a dedicated processor and firmware. The log storage unit 13 is a storage device such as an HDD or an SDD (Solid State Drive). The communication counter 14, the log temporary storage unit 15, and the reception request storage unit 16 are semiconductor storage devices.

  The communication log recording device 10 may be configured by a computer device 60. FIG. 4 is a diagram showing the configuration of the computer device 60. As shown in FIG. The computer device 60 includes a processor 61, a main storage 63, and an external storage 62 connected to one another by a bus 64.

  The processor 61 reads and writes data from and to the main storage 63 and the external storage 62 via the bus 64. The processor 61 also executes the communication log recording program 65 stored in the main storage device 63. The communication log recording program 65 may be initially stored in the external storage device 62, and the processor 61 may load the communication log recording program 65 from the external storage device 62 into the main storage device 63 when the computer 60 is initialized.

  Here, the main storage device 63 is a semiconductor storage device. The external storage device 62 is a storage device such as an HDD or an SDD.

  The processor 61 of the computer device 60 functions as the log collecting unit 11, the log storage unit 12, the communication processing unit 21, and the communication waiting unit 22 by executing the communication log recording program 65. That is, the processor 61 executes the communication log recording program 65 to execute the processing performed by the log collecting unit 11, the log storage unit 12, the communication processing unit 21, and the communication waiting unit 22.

  The main storage device 63 is used as the communication counter 14, the temporary log storage unit 15, and the reception request storage unit 16. The external storage device 62 is used as the log storage unit 13.

<Operation>
FIG. 5 is a flowchart showing the operation of the log collection unit 11 when communication is requested.

  The log collecting unit 11 is activated when the application 17 requests communication. When activated, the log collecting unit 11 requests the communication processing unit 21 to start communication (S11). Thereafter, the log collecting unit 11 generates a log ID with reference to the communication counter 14 (S12), and stores the log ID, the communication procedure, the execution result, and the end flag in an available line of the temporary log storage unit 15. (S13). Here, as the execution result, for example, a value reported from the communication processing unit 21 is set. The end flag is set to 0.

  Thereafter, the log collecting unit 11 requests the log storage unit 12 to store the communication log in the log storage unit 13 again if the log temporary storage unit 15 has an unsaved communication log with the end flag 1 and 1 S14). It is the communication log about the communication performed in the past what is stored again here. FIG. 7 is a flowchart of this operation, which will be described later.

  When the started communication is blocking type communication (YES in S15), the log collection unit 11 waits for the communication end by the communication waiting unit 22, sets the end flag of the communication log stored in S14 to 1, and The obtained execution result is stored in the temporary log storage unit 15 (S17). In the case of reception, the log collection unit 11 also stores the received data obtained from the communication waiting unit 22 in the temporary log storage unit 15. Thereafter, the log collecting unit 11 ends the process.

  When the started communication is non-blocking type communication (NO in S15, YES in S16), the log collecting unit 11 stores the reception request ID and the log ID in an available line of the reception request storage unit 16 (S18). Thereafter, the log collecting unit 11 ends the process.

  If the communication started is, for example, transmission (NO in S15, NO in S16), the log collecting unit 11 ends the process.

  FIG. 6 is a flow chart showing the operation of the log collection unit 11 when receiving a termination waiting request for non-blocking communication.

  The application 17 is activated when a request for termination waiting for non-blocking communication is requested, and the log collecting unit 11 causes the communication waiting unit 22 to wait for termination of communication specified by the input reception request ID (S21). When the designated communication is completed, the log collecting unit 11 searches the reception request storage unit 16 and acquires the log ID from the line in which the reception request ID matches the designated reception request ID (S22).

  Next, the log collecting unit 11 searches the log temporary storage unit 15, accesses the communication log whose log ID matches the log ID acquired in the previous step, sets the end flag to 1, and from the communication waiting unit 22 The obtained execution result is stored (S23). In the case of reception, the log collection unit 11 also stores the received data obtained from the communication waiting unit 22 in the communication log. Thereafter, the log collection unit 11 deletes the data of the line accessed in S22 from the reception request storage unit 16 (S24), and ends the process.

  The log collecting unit 11 may provide the application 17 with an end confirmation request in addition to the end waiting request as an interface for synchronizing the end of the non-blocking type communication. When the end confirmation is requested, the log collecting unit 11 checks the end of the communication and executes the steps after S22 if it is ended instead of the step S21, and reports the fact to the application 17 if it is not ended. Just do it.

  FIG. 7 is a flowchart showing the operation of the log storage unit 12. This flowchart is for describing the process of S14 in FIG. 5 in detail.

  The log storage unit 12 activated from the log collecting unit 11 has a communication in progress and a communication log with an end flag 1 is present in the log temporary storage unit 15 (YES in S31), the log temporary storage unit 15 The communication log having the end flag set to 1 is read out from the file and stored in the log storage unit 13 (S32, S33). That is, the log storage unit 12 stores the communication log whose end flag is 1 from the temporary log storage unit 15 back to the log storage unit 13. Thereafter, the log storage unit 12 deletes the communication log that has been stored in the log storage unit 13 from the temporary log storage unit 15 (S34), and returns to S31.

  If there is no communication in progress or there is no communication log with an end flag of 1 in the log temporary storage unit 15 (NO in S31), the log storage unit 12 ends the process and restarts the log collection unit 11.

<Effect>
The communication log recording device 10 according to the present embodiment buffers the communication log in the temporary log storage unit 15 such as the main storage, and stores the communication log in the log storage unit 13 such as the HDD later. It is possible to suppress the influence of input / output for re-storing on other processing. The reason is that, while the log storage unit 12 is executing communication, the communication log stored in the temporary log storage unit 15 is stored again in the log storage unit 13.

  By using the communication waiting time for storing the communication log from the log temporary storage unit 15 to the log storage unit 13 again, the communication log recording device 10 is used for calculation without using asynchronous input / output. It is possible to reduce the increase in execution time accompanying the movement of the communication log without reducing the CPU resources required.

  FIG. 8 shows the execution of the case where the communication log of the communication is saved immediately after the end of communication in the timeline (A in the figure) and in the case of the communication log recording device 10 according to the present embodiment (B in the figure) It represents the difference in time. For example, the communication log recording device 10 according to the present embodiment does not perform storage of the communication log of the communication a again after the end of the communication a, but performs the timing so as to perform in parallel during the execution of the next communication b. Has been changed (arrows in the figure). As a result, the communication log recording device 10 prevents the calculation delay of the application 17 that occurs when the communication log of the communication a is stored again by the synchronous input / output. Further, when the communication log recording device 10 stores the communication log of the communication a again by the asynchronous input / output, the influence (the overhead of context change, etc.) on the calculation of the application 17 is given by the input / output. It can be prevented.

Second Embodiment
<Configuration and operation>
The communication log recording device 10 according to the present embodiment includes a general-purpose operating system (OS), and executes a plurality of processes in parallel. The log collecting unit 11, the log storage unit 12, the application 17, the communication processing unit 21, and the communication waiting unit 22 are activated by a process. The communication log recording device 10 according to the present embodiment includes a log storage unit 13, a communication counter 14, a temporary log storage unit 15, and a reception request storage unit 16 for each process. However, the log storage unit 13 and the log temporary storage unit 15 can be accessed from other processes.

  FIG. 9 is a diagram showing the configuration of the temporary log storage unit 15 in the present embodiment. The temporary log storage unit 15 of each process is arranged on the inter-process shared memory of the communication log recording device 10. The temporary log storage unit 15 for each process is the same as that of the first embodiment.

  The log collecting unit 11 stores, for each process, a communication log that reflects the communication of the activated process (also referred to as the own process) in the temporary log storage unit 15 provided in the own process. The log storage unit 12 stores the communication log of the temporary log storage unit 15 provided in the own process again in the log storage unit 13 provided in the own process. However, if the communication log whose end flag is 1 does not exist in the log temporary storage unit 15 provided in the own process, the communication log of the log temporary storage unit 15 provided in processes other than the own process (also referred to as other processes) , And stored again in the log storage unit 13 provided in the other process.

  FIG. 10 is a flowchart showing the operation of the log storage unit 12 according to the present embodiment. When activated from the log collection unit 11 activated in the process, the log storage unit 12 first checks whether the next process starts and there is a communication that is being executed, ie, not completed yet, if not (S41 End the process.

  If there is a communication in progress (YES in S41), the log storage unit 12 checks whether a communication log having an end flag of 1 exists in the log temporary storage unit 15 of the own process. If it exists (YES in S42), the log storage unit 12 stores the communication log of the log temporary storage unit 15 provided in its own process back into the log storage unit 13 provided in its own process, and the communication log is stored. The temporary log storage unit 15 is deleted (S43 to S45), and the process returns to S41.

  If not (NO at S42), the log storage unit 12 checks if there is a communication log whose end flag is 1 in the log temporary storage unit 15 of another process. If it exists (YES in S46), the log storage unit 12 stores the communication log of the log temporary storage unit 15 provided in the other process back into the log storage unit 13 provided in the other process, and the communication The log is deleted from the log temporary storage unit 15 (S47 to S49), and the process returns to S41.

<Effect>
The communication log recording device 10 according to the present embodiment uses the communication waiting time of a certain process for storing the communication log of another process from the temporary log storage unit 15 into the log storage unit 13 again, as described above. Can produce the same effect. The reason is that the log storage unit 12 stores the communication log of the temporary log storage unit 15 provided in the other process again in the log storage unit 13 provided in the other process.

  FIG. 11 shows the effect of the communication log recording device 10 according to the present embodiment in a timeline. In the figure, it is assumed that the communication log of the communication a executed by the process A is acquired by the log temporary storage unit 15, and no communication waiting occurs in the subsequent communication b. In this case, in the communication log recording device 10 of the first embodiment, the communication log of the communication a is left in the temporary log storage unit 15 of the process A for a long time. In the worst case, re-storage in the log storage unit 13 occurs in the end processing of the process A, and the end processing is delayed.

  In the communication log recording device 10 of the present embodiment, the communication log of the communication a of the process A uses the communication waiting time of the communication d of the other process B to store the log from the log temporary storage unit 15 of the process A It is stored again in the unit 13. Thereby, the above-mentioned processing delay can be prevented.

Third Embodiment
When the received data is very large, the time to store the communication log from the log temporary storage unit 15 to the log storage unit 13 may be longer than the communication execution time. In this case, the processing of the application 17 is delayed by the excess time. In order to prevent this, the communication log recording device 10 according to the present embodiment divides and stores the communication log not into communication log units but into a plurality of sections.

  FIG. 12 is a diagram showing the configuration of the communication log recording device 10 according to the present embodiment. The communication log recording device 10 according to the present embodiment includes a stored information storage unit 18 in addition to the configuration of the communication log recording device 10 of the first embodiment. The storage information storage unit 18 stores storage information indicating up to which section divided into a predetermined size has been re-stored from the temporary log storage unit 15 into the log storage unit 13, that is, stored.

  When detecting that the size of the communication log is equal to or more than the predetermined number of bytes, the log storage unit 12 divides the communication log into sections of a predetermined size, and one section at a time from the top each time communication execution end waiting occurs Are stored again from the temporary log storage unit 15 into the log storage unit 13. In the process, the log storage unit 12 records in the storage information storage unit 18 up to which section of the communication log the storage has been stored again, that is, it has been stored. The log storage unit 12 stores the next section indicated by the storage information storage unit 18 again from the temporary log storage unit 15 into the log storage unit 13 each time waiting for execution end of communication occurs. The log storage unit 12 repeats this operation until the restorage of all partitions is completed, and after the end, the communication log is deleted from the temporary log storage unit 15.

Fourth Embodiment
FIG. 13 is a diagram showing the configuration of the communication log recording device 10 according to the present embodiment. The communication log recording device 10 according to the present embodiment includes a log storage unit 13, a temporary log storage unit 15 faster than the log storage unit 13, a log collection unit 11, and a log storage unit 12.

  When receiving the reception request, the log collection unit 11 generates a log ID indicating the issuance order of the reception request and starts reception, and temporarily stores log information including the log ID and the received data read at the end of the reception. Store in section 15. The log storage unit 12 stores the log information stored in the temporary log storage unit 15 back into the log storage unit 13 after the requested transmission or reception is started.

  The communication log recording device 10 according to the present embodiment buffers the communication log in the temporary log storage unit 15 such as the main storage, and stores the communication log in the log storage unit 13 such as the HDD later. It is possible to suppress the influence of input / output for re-storing on other processing. The reason is that, while the log storage unit 12 is executing communication, the communication log stored in the temporary log storage unit 15 is stored again in the log storage unit 13.

  As mentioned above, although this invention was demonstrated with reference to embodiment, this invention is not limited to the said embodiment. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

DESCRIPTION OF REFERENCE NUMERALS 10 communication log recording apparatus 11 log collecting unit 12 log storage unit 13 log storage unit 14 communication counter 15 log temporary storage unit 16 reception request storage unit 17 application 18 storage information storage unit 21 communication processing unit 22 communication waiting unit 60 computer device 61 processor 62 external storage 63 main storage 64 bus 65 communication log recording program

Claims (10)

Log storage means,
Temporary log storage means faster than the log storage means;
When the reception request is received, generation of the log ID indicating the issuance order of the reception request and start of reception are performed, and log information including the log ID and the received data read at the end of the reception is stored in the temporary log storage unit Log collection means to be stored;
A communication log recording device, comprising: log storage means for storing the log information stored in the temporary log storage means back into the log storage means after the requested transmission or the reception is started.   The log collecting means, upon receiving the synchronous type reception request, generates the log ID and starts the reception, and after waiting for the end of the reception, the log information including the generated log ID and the reception data The communication log recording apparatus according to claim 1, wherein the temporary log storage means stores the log. It further comprises reception request storage means for storing the reception request ID identifying the asynchronous reception request being executed and the log ID in association with each other.
The log collection means 1) processing of generating the log ID and acquiring the reception request ID upon reception of the asynchronous reception request, associating the both with each other, and storing them in the reception request storage means; After executing the process of starting the reception, the execution of the application that issued the reception request is resumed, and 2) the reception request storage means is associated with the reception request ID of the reception that is ended when the reception is ended. The communication log recording apparatus according to claim 1, wherein the log ID stored in and the log information including the received data are stored in the temporary log storage unit. The log storage unit and the temporary log storage unit are provided for each process executed by the communication log recording device.
The log collecting means is activated by each of the processes, and stores the log information in the temporary log storage means provided in the activated process.
The log storage means is executed by each of the processes, and the log information stored in the temporary log storage means provided in the process other than the process being started is The communication log recording device according to any one of claims 1 to 3, wherein the log storage means provided in the process is stored again. Storage information storage means for storing storage information indicating to which section the log information is divided into predetermined sizes is stored in the log storage means;
The log storage means stores again the next section indicated by the storage information from the log temporary storage means into the log storage means, and records the section as saved in the storage information. The communication log recording device of any one of 4. When a reception request is received, generation and reception of a log ID indicating the issuance order of the reception request are started, and log information including the log ID and the received data read at the end of the reception is faster than the log storage means Store in temporary log storage means,
A communication log recording method, wherein the log information in the temporary log storage means is stored again in the log storage means after the requested transmission or the reception is started.   When the synchronous type reception request is received, generation of the log ID and start of the reception are performed, and after waiting for the end of the reception, the temporary storage unit of the log information including the generated log ID and the reception data The communication log recording method according to claim 6, which is stored in   1) Upon receipt of the asynchronous reception request, the generation of the log ID and acquisition of the reception request ID for identifying the asynchronous reception request being executed are performed, and both are associated and stored in the reception request storage means After execution of the processing and the processing for starting the reception, the execution of the application that has issued the reception request is resumed, and 2) at the end of the reception, it is associated with the reception request ID of the reception that is terminated 7. The communication log recording method according to claim 6, wherein said log ID stored in said reception request storage means and said log information including said received data are stored in said log temporary storage means. A computer comprising: log storage means; and temporary log storage means faster than said log storage means;
When the reception request is received, generation of the log ID indicating the issuance order of the reception request and start of reception are performed, and log information including the log ID and the received data read at the end of the reception is stored in the temporary log storage unit Log collection processing to be stored,
A communication log recording program for executing a log storage process of storing the log information stored in the temporary log storage means back into the log storage means after the requested transmission or the reception is started.   When the synchronous type reception request is received, generation of the log ID and start of the reception are performed, and after waiting for the end of the reception, the temporary storage unit of the log information including the generated log ID and the reception data 10. The communication log recording program according to claim 9, making the computer execute the log collecting process stored in.

Images