Adaptor trace information is output under the following name:

adp_type-adaptor-group-name-adaptor-name_serial-number

The following describes each component of the file name:

• type
  One of the following is set:
  IN: This value is set for an input adaptor.
  OUT: This value is set for an output adaptor.
  
• adaptor-group-name
  This is the value specified in the name attribute in the adaptor group definition.
  
• adaptor-name
  This is the value specified in the name attribute in the adaptor definition
  
• serial-number
  This is a serial number for the file. A value in the range from 001 to 004 is set.
  

If the adaptor trace file already exists when the adaptor starts, its file name is changed to file-name.bk.

For details about the adaptor definition files, see 9. Adaptor Definition Files.

Adaptor trace information is output in CSV format, as shown below:

number,date,time,thread,event

The table below describes each output item.

Table 6-6 Items output as adaptor trace information

callback-name{entry|exit}

An example of the output is shown below. In this example, the first line is a header and the subsequent lines are records.

No,Date,Time,Thread,Event
0001,2010/10/15,02:08:41.173,OutputAdaptor1,receiver entry
0002,2010/10/15,02:08:41.173,OutputAdaptor1,receiver exit
0003,2010/10/15,02:08:41.188,OutputAdaptor1,editor1 entry
0004,2010/10/15,02:08:41.188,OutputAdaptor1,editor1 exit
0005,2010/10/15,02:08:41.188,OutputAdaptor1,editor3 entry
0006,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 exit
0007,2010/10/15,02:08:41.204,OutputAdaptor1,outputer entry
0008,2010/10/15,02:08:41.204,OutputAdaptor1,outputer exit
0009,2010/10/15,02:08:41.204,OutputAdaptor1,receiver entry
0010,2010/10/15,02:08:41.204,OutputAdaptor1,receiver exit
0011,2010/10/15,02:08:41.204,OutputAdaptor1,editor1 entry
0012,2010/10/15,02:08:41.204,OutputAdaptor1,editor1 exit
0013,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 entry
0014,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 exit
0015,2010/10/15,02:08:41.204,OutputAdaptor1,outputer entry
0016,2010/10/15,02:08:41.204,OutputAdaptor1,outputer exit
  : 

This subsection describes the adaptor trace information that is output when records are discarded during callback processing or packets are discarded during HTTP packet input connector processing.

• When records are discarded during callback processing
  Each time callback is executed, the total number of records discarded immediately before the callback processing terminated is output to the adaptor trace file.
  In this case, the event output item in Table 6-6 Items output as adaptor trace information is output in the following format:
  callback-nameexecute deletedetailed-information
  
  • callback-name: Value specified in the name attribute in the CB definition
  • : Single-byte space
  • execute delete: Type of operation
  • detailed-information: Detailed information for the callback, as shown in the table below.
    

    Table 6-7 Detailed information in the adaptor trace information for a callback (applicable to discarding of records)

    No.	Callback type	Detailed information
    1	HTTP packet input connector	When records were discarded because the number of HTTP packets in the output buffer reached the maximum value:#1 recordoverflowdiscarded-records-count
    2	Filter	When records were discarded because a field condition was not satisfied:#2 conditionrecord-namediscarded-records-count
    3	Record extraction	When records were discarded because an extraction target condition was not satisfied:#3 conditionrecord-name#4discarded-records-count When records were discarded due to record duplication: samerecordname-of-record-to-be-extracteddiscarded-records-count When records were discarded due to a timeout:#5 timeoutextraction-condition-namediscarded-records-count When records were discarded because the maximum number of records that can be retained had been reached:#6 overflowdiscarded-records-count When records were discarded due to a record out-of-sequence time: timereversediscarded-records-count
    4	Dashboard output connector	When records were discarded because the record retention period#7 had elapsed: timeoutdiscarded-records-count When records were discarded because the maximum number of records that can be retained had been reached:#8 overflowdiscarded-records-count When records were discarded due to deletion of collected records:#9 readdiscarded-records-count

    #1

    The maximum number of HTTP packets that can be stored in the output buffer is specified in the buffersize attribute of the input tag in the HTTP packet input connector definition. For details about the buffersize attribute, see 9.10.2 HTTP packet input connector definition.

    #2

    A field condition is specified in the field tag in the filter definition. For details about the field tag, see 9.11.3 Filter definition.

    #3

    An extraction target condition is specified in the targetrecord tag in the record extraction definition. For details about the targetrecord tag, see 9.11.4 Record extraction definition.

    #4

    If none of the extraction target conditions is satisfied, the name of the record being discarded is output; if an extraction condition is not satisfied, the name of the extraction target record is output.

    #5

    The timeout value is specified in the timelimit attribute of the extraction tag in the record extraction definition. For details about the timelimit attribute, see 9.11.4 Record extraction definition.

    #6

    The maximum number of records that can be retained is specified in the size attribute of the extractions tag in the record extraction definition. For details about the size attribute, see 9.11.4 Record extraction definition.

    #7

    The record retention period is specified in the RecordHoldTime tag in the dashboard output connector definition. For details about the RecordHoldTime tag, see 9.10.4 Dashboard output connector definition.

    #8

    The maximum number of records that can be retained is specified in the MaxNum attribute of the DashboardOutputConnectorDefinition tag in the dashboard output connector definition. For details about the MaxNum attribute, see 9.10.4 Dashboard output connector definition.

    #9

    Deletion of collected records is specified in the ReadRecordRemoveFlag attribute of the DashboardOutputConnectorDefinition tag in the dashboard output connector definition. For details about the ReadRecordRemoveFlag attribute, see 9.10.4 Dashboard output connector definition.

    
    

The following shows examples of output of adaptor trace information for callbacks:

1. HTTP packet input connector
   This example discarded 50 excess records because the number of records to be stored in the output buffer for the HTTP packet input connector (callback name: inputer) exceeded the maximum value.
   

   3288,2010/10/15,10:16:11.223,InputAdaptor1,inputer entry 3289,2010/10/15,10:16:11.223,InputAdaptor1,inputer execute delete record overflow 50 3290,2010/10/15,10:16:11.223,InputAdaptor1,inputer exit

2. Filter
   This example discarded 100 records (R1) that did not satisfy a field condition for filtering (callback name: filter1):
   

   3291,2010/10/15,10:16:11.223,InputAdaptor1,filter1 entry 3292,2010/10/15,10:16:11.223,InputAdaptor1,filter1 execute delete condition R1 100 3293,2010/10/15,10:16:11.223,InputAdaptor1,filter1 exit

3. Record extraction
   This example discarded 10 records that did not satisfy an extraction target record condition (conditionE2) for record extraction (callback name: extract1):
   

   3294,2010/10/15,10:16:11.223,InputAdaptor1,extract1 entry 3295,2010/10/15,10:16:11.223,InputAdaptor1,extract1 execute delete condition conditionE2 10 3296,2010/10/15,10:16:11.223,InputAdaptor1,extract1 exit

4. Dashboard output connector
   This example discarded 20 records because the number of records to be retained by the dashboard output connector (outputer) reached the maximum value:
   

   3288,2010/10/15,10:16:11.223,OutputAdaptor1,outputer entry 3289,2010/10/15,10:16:11.223,OutputAdaptor1,outputer execute delete numoverflow 20 3290,2010/10/15,10:16:11.223,OutputAdaptor1,outputer exit

• When HTTP packets or messages are discarded by the HTTP packet input connector
  Each time HTTP packet input connector processing is performed, the total number of HTTP packets or HTTP messages discarded before the processing terminated is output to the adaptor trace file.
  In this case, the event output item in Table 6-6 Items output as adaptor trace information is output in the following format:
  callback-nameexecute deletedetailed-information
  
  • callback-name: Value specified in the name attribute in the CB definition
  • : Single-byte space
  • execute delete: Type of operation
  • detailed-information: Detailed information
    

    Table 6-8 Detailed information in the adaptor trace information (applicable to discarding of packets or HTTP messages)

    Callback type	Detailed information
    HTTP packet input connector	When HTTP packets were discarded because the number of HTTP packets in the input buffer reached the maximum value:#1 packetoverflowdiscarded-packets-or-HTTP-messages-count When HTTP messages were discarded because the packet segment assembly time#2 resulted in a timeout: httpmessagetimeoutdiscarded-packets-or-HTTP-messages-count

    #1

    The maximum number of HTTP packets that can be stored in the input buffer is specified in the buffersize attribute of the input tag in the HTTP packet input connector definition. For details about the buffersize attribute, see 9.10.2 HTTP packet input connector definition.

    #2

    The packet segment assembly time is specified in the assemblingtime attribute of the input tag in the HTTP packet input connector definition. For details about the assemblingtime attribute, see 9.10.2 HTTP packet input connector definition.

    
    
  The following shows examples of output of adaptor trace information:
  
  • This example discarded 20 excess packets because the number of packets to be stored in the input buffer exceeded the maximum value:
    

    3288,2010/10/15,10:16:11.223,InputAdaptor1,inputer entry 3289,2010/10/15,10:16:11.223,InputAdaptor1,inputer execute delete packet overflow 20 3291,2010/10/15,10:16:11.223,InputAdaptor1,inputer exit

  • This example discarded 5 HTTP messages because the packet segment assembly time resulted in a timeout:
    

    3288,2010/10/15,10:16:11.223,InputAdaptor1,inputer entry 3290,2010/10/15,10:16:11.223,InputAdaptor1,inputer execute delete httpmessage timeout 5 3291,2010/10/15,10:16:11.223,InputAdaptor1,inputer exit