Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » Relay Server » Relay Server logging and log administration

 

Outbound Enabler Record

You can use the Outbound Enabler Record (OER) to diagnose relay failures and study performance. The OER consists of a concise summary of the Outbound Enabler processing of a single request and includes information about requests, timing, important debugging information, request status, and data volumes. The Outbound Enabler Record is generated as part of the Outbound Enabler log when verbosity is set to 1 or higher. There is one OER data line per HTTP request.

The Outbound Enabler Record is comprised of a set of data types (represented by symbols) and values. The symbols and their associated data types are listed in the following table:

Symbol Data type
b: Byte count
c: General numeric counter
i: ID or numeric code
m: Time measured in milliseconds
x: Hex number
name:string Variable length named string values. This may include: user agent information, affinity information, cookie information, Outbound Enabler errors, Outbound Enabler error parameters, the name of the Relay Server, Relay Server error names, and the label.
up Element associated with the relaying request (excluding the response) to the backend
rtp Element associated with round-trip transport and processing of the last up and first down packet
dn Element associated with the relaying request (excluding the response) from the backend to the Relay Server

The symbols are compounded together (as field names) to refer to particular kinds of data. For example, b:up.maxReqQ corresponds to the byte count (b:) of the peak memory usage of the per-request upward (up) packet queue (maxReqQ).

Field name Data type
i:oidx Relay Server index in the Relay Server farm
i:ridx Temporary request index assigned by the Relay Server
i:sidx Application session index assigned by the Outbound Enabler to the first request
x:snum Session serial number assigned by the Relay Server to the first request
x:sfp Session fingerprint assigned by the Relay Server on the first request
m:up Request relaying period starting from the sending of the first request packet to the sending of the last request packet
m:rtp Round-trip processing period from the sending of the last request packet to the receiving of the first response packet between the Outbound Enabler and the backend server, including the backend processing time
m:dn Response relaying period starting from the arrival of the first response packet to the arrival of the last response packet
m:close Idle period from the arrival of the last response packet to the garbage collection or reuse of the affinity context
b:up.maxReqQ Peak memory usage of the per-request upward packet queue
b:dn.maxShrQ Peak memory usage of the shared downward packet queue during the response relaying period of this request
i:err Error ID
err.p0 First error parameter from the Outbound Enabler
err.p1 Second error parameter from the Outbound Enabler
err.p2 Third error parameter from the Outbound Enabler

An Outbound Enabler Record looks similar to the following sample:

I. 2012-11-09 02:35:12.821-0500 <OEHost> OER header:   i:oidx     i:ridx     i:sidx     x:snum      x:sfp |       m:up      m:rtp       m:dn    m:close | b:up.maxReqQ b:dn.maxShrQ |  i:err ...other-variable-length-elements...
I. 2012-11-09 02:35:41.070-0500 <Backend-0000> OER row:     0          0          0          0   d9d72990 |       2364        999         23      20620 |        49723        65455 |      0 <err:OEE_NO_ERROR> <err.p0:> <err.p1:> <err.p2:>
I. 2012-11-09 02:36:05.153-0500 <Backend-0000> OER row:     0          0          0          0   d9d72990 |       2439        999         21      20615 |        56968        65455 |      0 <err:OEE_NO_ERROR> <err.p0:> <err.p1:> <err.p2:>
I. 2012-11-09 02:36:08.614-0500 <Backend-0000> OER row:     0          0          0          0   d9d72990 |       2439        999         21          0 |        56968        65455 |      0 <err:OEE_NO_ERROR> <err.p0:> <err.p1:> <err.p2:>
I. 2012-11-09 03:53:12.362-0500 <Backend-0000> OER row:     0          0          1          0   87293f45 |          0          0          0          0 |            0            0 |   1029 <err:OEE_RS_IDX_NOT_FOUND> <err.p0:61166> <err.p1:> <err.p2:>
 See also