Output formats

The Exception trace log has the following four formats.

Format 1: Header section

 
[AA....AA] HiRDB_Type4_JDBC_Driver BB-CC

Format 2: Method execution history (execution start of a method)

 
AAAAAAAAAAAAAAAAAAAAAAA BB....BB:[C][DD....DD]
                        ConnectionID(EE....EE) : SID(FF....FF)
                        GG....GG

Format 3: Method execution history (normal termination of a method)

 
AAAAAAAAAAAAAAAAAAAAAAA BB....BB:[C][DD....DD]
                        ConnectionID(EE....EE) : SID(FF....FF)
                        HH....HH

Format 4: Timing when output occurred

 
AAAAAAAAAAAAAAAAAAAAAAA BB....BB:Exception:
II....II

Format 2 and Format 3 are output repeatedly in time series sequence for each method executed.

Organization of this subsection: (1) Explanation of variables in Format 1; (2) Explanation of variables in Format 2, Format 3, and Format 4

AAAAAAAAAAAAAAAAAAAAAAA

Indicates the acquisition date and time of the Exception trace log, in the following format (a value from 0 to 9 is set in each variable):

 
YYYY/MM/DD hh:mm:ss.sss

YYYY: Year (Western calendar)

MM: Month

DD: Day

hh: Hour (24-hour clock format)

mm: Minute

ss.sss: Second (includes 3 digits after the decimal point)

BB....BB

Indicates thread identification information for the target thread, in the following format:

 
Thread[aa....aa]@bb....bb

aa....aa: Thread information, including the thread name, priority sequence, and thread group name. The Java Virtual Machine determines the format.

bb....bb: Hash code of the object. The Java Virtual Machine determines the format.

C

Indicates call identification information for the method:

E: Indicates that the information is history information for when the method was started.

R: Indicates that the information is history information for when the method terminated normally.

DD....DD

Indicates the object identifier and the method name, in the following format:

 
aa....aa.bb....bb

aa....aa: Object identifier (up to 32 characters): The Java Virtual Machine determines the format.

bb....bb: Method name

EE....EE

Indicates the connection ID, in the following format:

 
aa....aa:bb....bb:cc....cc

aa....aa: Front-end server name or single-server name (up to 32 characters).: If this information cannot be retrieved, an asterisk (*) is output.

bb....bb: Connection sequence number (up to 10 characters) of the server identified by aa....aa.: If this information cannot be retrieved, an asterisk (*) is output.

cc....cc: Process ID (up to 10 characters) of the server identified by aa....aa.: If this information cannot be retrieved, an asterisk (*) is output.

FF....FF: Indicates the section ID (up to 4 characters).

GG....GG

Indicates the method arguments, in the following format (this information is not output for methods without arguments):

 
aa....aa=bb....bb
aa....aa=bb....bb
        :
aa....aa=bb....bb

aa....aa: Argument name.

bb....bb: Argument contents (up to 256 characters).: For reference type values, the object determines the format.

One asterisk (*) is output to bb....bb for the password argument of the following methods:

getConnection(String username, String password) of the DataSource class
getPooledConnection(String username, String password) of the ConnectionPoolDataSource
getXAConnection(String username, String password) of XADataSource

For the info argument in connect(String url,Properties info) of the Driver class, the value of the each of the following properties is replaced by one asterisk (*) and then output:

password
HiRDB_for_Java_ENV_VARIABLES

HH....HH

Indicates the return value of the method, in the following format:

 
Return=aa....aa

aa....aa: Argument name.

This item is not output for methods that do not have a return value. If the return value is a reference-type value, the Java Virtual Machine determines the format.

II....II

Indicates troubleshooting information, in the following format:

 
ExceptionClass: aa....aa
UapEnvironment: bb....bb
Message: cc....cc
ErrorCode: dd....dd
SQLState: eeeee
UpdateCounts: ff....ff, ....<omitted>,ff....ff
Etc.: gg....gg, hh....hh, iiii
jj....jj

aa....aa: Effective class name of the exception object that was thrown.

bb....bb: Client environment definitions being used in the connection of the exception object. The definitions are output in the following format (if no definitions are to be output, this variable is replaced by an asterisk (*) and then output):

 
yy....yy (zz....zz), ...<omitted>, yy....yy (zz....zz)

yy....yy: Name of the client environment definition without the initial PD characters. The following client environment definitions are the output targets:

PDHOST
PDNAMEPORT
PDFESHOST
PDSERVICEGRP
PDSRVTYPE
PDSERVICEPORT
PDCLTRCVPORT
PDCLTRCVADDR
PDUSER
PDCWAITTIME
PDSWAITTIME
PDSWATCHTIME

zz....zz: Contents of the client environment definition. The password portion of PDUSER is not output.

cc....cc: Message of the exception object.

dd....dd: SQLCODE error code (for XAException, error code indicated by the errorCode field of the XAException object) (up to 11 characters).

This item is output when the effective class of the thrown exception object is one of the following classes or subclasses:

SQLException
XAException

eeeee: SQLSTATE (5 characters).: This item is output when the effective class of the thrown exception object is SQLException or a subclasss of SQLException.

ff....ff: Number of update rows for each update statement in a batch update that was executed normally before this exception occurred (up to 11 characters).: This item is output when the effective class of the exception object is BatchUpdateException.; If the number of update rows cannot be obtained, an asterisk (*) is output.

gg....gg: SQL counter value (up to 11 characters).: This information can be used for coordinating with the trace information output by the SQL trace facility.; If the SQL counter cannot be obtained, an asterisk (*) is output.

hh....hh: Failure information of the HiRDB server when an error occurs in the HiRDB server (up to 22 characters).: The failure information is used by maintenance personnel.; If no errors have occurred in the HiRDB server, an asterisk (*) is output.

iiii: Type of request (operation code) that the JDBC driver issued to the HiRDB server when an error occurred in the HiRDB server.: If no errors have occurred in the HiRDB server, an asterisk (*) is output.

jj....jj: Stack trace in which the exception-throwing method is set as the base point.: The Java Virtual Machine determines the format.

17.13.2 Output formats

(1) Explanation of variables in Format 1

(2) Explanation of variables in Format 2, Format 3, and Format 4