OpenTP1 Version 7 Messages

[Contents][Index][Back][Next]

KFCA00339-W

rpc request is canceled to callers rpc timedout. server=aa...aa, pid=bb...bb, callers node address=cc...cc, callers port=dd...dd, type=ee...ee, reception time of rpc request=ff....ff, server side acquisition time=gg....gg, wait time of rpc call source=hh....hh

The SPP that used dc_rpc_call to receive a service request detected a timeout at the client UAP that requested the service. So SPP canceled this service request because it would be pointless to process the service and make a response.
aa...aa: Server name of the SPP that canceled the RPC request
bb...bb: Process ID of the SPP that canceled the RPC request
cc...cc: IP address in dot (.) format for the service caller UAP
dd...dd: Receiving port number (listen port number) of the service caller UAP
ee...ee: Type code, showing either of the following.
1: When the SPP accepted a service, the SPP that used dc_rpc_call to receive a service request detected a timeout at the client UAP that requested the service.
2: When the SPP executed the service function, the SPP that used dc_rpc_call to receive a service request detected a timeout at the client UAP that requested the service.
ff....ff: Number of seconds from the reception of the RPC request (decimal)
For the server for which queue is specified for the receive_from operand in the user service definition, ff....ff indicates the time elapsed after the request message was queued. For the server for which socket is specified, ff....ff indicates the time elapsed after the request message was received.
gg....gg: Number of seconds from the acquisition of the message on the server (decimal)
For type code 1, gg....gg indicates the time elapsed after the request message was taken from the queue. For type code 2, gg....gg indicates the time elapsed after the service function was executed.
hh....hh: Wait time of the RPC caller UAP (unit: seconds) (decimal)
S: Continues processing.