sr java.lang.Integer⠤8 I valuexr java.lang.Number xp t*bundleresource://131.fwk-569085495:6/META-INF/trace.xml=
This group provides tracing for all ODC events.
An ODC node property change event was ignored for one of the following reasons:
(1) the new value is the same as the old value;
(2) the priority of the old value is higher than the priority of the new value.
Name of the ODC transaction making tree changes
An ODC node is added or deleted
An ODC edge is added or deleted
An ODC node property is changed
Contains records used by the trace facility
The record that is written to beginning of each file.
The path of the file.
The fully qualified process name of the form: cell/node/process
This record is written to the beginning of each block of trace information to identify the
writer of the following records.
A count to uniquely identify the instance of the following trace records.
;bundleresource://131.fwk-569085495:7/META-INF/trace.xml=
The replayer input dump is for IBM development use only.
The replayer output dump is for IBM development use only.
ARFM (Autonomic Request Flow Manager) dynamically regulates the flow of HTTP requests, SIP messages, IIOP calls, and JMS MDB messages.
The ARFM controller receives statistics from various sources. Based upon
those statistics and upon service policy configuration, the ARFM controller
then controls how traffic is processed by the ARFM gateways. The ARFM gateways
are in the ODR process for HTTP and SIP traffic, and in the application server
process for IIOP and JMS traffic.
The name of this flow.
The number of virtual seats allocated.
The first tier work factor (alpha).
The utility value.
The average queue length.
Average number executing.
Average service time.
Average response time.
Average wait time in the queue.
The maximum of maxExec and the average concurrency allocation, in physical seats.
The message arrival rate, in msgs/sec, averaged over the last control cycle.
The admission rate of messages that initiate logical dialogs.
The rate of messages that (a) were enqueued during the reported interval,
(b) are not retransmissions of earlier messages, and (c) initiate a logical dialog.
The rate of requests dispatched from the queue to a server.
The rate of message completions.
The rate of dropped messages.
The service time variance.
A QStat record contains statistics for a particular gateway, where a gateway is identified
by a (protocolSuite,ODR,deploymentTarget) tuple. For example, there is a gateway for
HTTP traffic flowing through ODR cell1/node1/odr1 to cluster cell1/cluster1.
Unique identifier for the ARFM gateway. The format is protocol:deploymentTarget:cell_node_odr.
For HTTP, 'protocol' is the empty string.
Average queue length for this flow.
Average number executing.
Average service time of requests that completed during the measurement interval.
Average response time of requests that completed during the measurement interval.
Average wait time in the queue for requests dispatched during the measurement interval.
Maximum number executing during the measurement interval.
The number of requests that arrived during the measurement interval.
The number admitted is this value less the number not admitted
(see 'dropped' field for how to count those).
The number of messages that (a) were enqueued during the reported interval,
(b) are not retransmissions of earlier messages, and (c) initiate a logical dialog.
The number of requests dispatched from the queue to server during the measurement interval.
The number of requests whose execution completed during the measurement interval.
The number of requests that (1) arrived during the measurement interval and (2) were not immediately dispatched or dropped.
The longest successful service time seen during the most recent high water mark period.
The sum, over each millisecond in the measurement interval,
of the number of requests that were estimated to be stuck executing at the start of the millisecond.
The number of requests that completed during the reported interval and had a response time above the service class threshold.
The number of requests dropped from any reason during the measurement interval.
The number of requests that were initially accepted into the queue and then, at some time during the reported interval, ejected from the queue.
The number of requests that completed during the measurement interval due to service timeout.
The number of requests that completed during the measurement interval with an error.
The sum, over the requests whose execution completed during the measurement interval, of the square of the request's service time. The sum is in units of milliseconds. Divide by serviced to get average.
Describes the computational power available in a given target cell.
Node name.
Node speed.
Background speed.
Describes the computational power assigned to each Dynamic Cluster by APC.
Cluster name.
Cluster power.
Describes the utility function generated by ARFM for each dynamic cluster.
Cluster name.
Maximum allocation requested.
The speed request in units of work/sec.
A connection failure can occur when the ODR cannot connect to a
back-end server.
In-session HTTP requests contain a session cookie (or session ID encoded in the URL) which
identify not only the session to the application, but the server to the On-Demand Router.
This entry indicates that a request contained a session ID, that the target server has been located,
and that affinity to it may be preserved.
When a session is established through an IBM HTTP Server (IHS) and an On-Demand Router (ODR) to an application server in
an environment where the IHS fronts multiple cells, then for in-session requests, it is necessary to instruct the IHS
to route to the same ODR -- i.e., the IHS must preserve ODR affinity. If the IHS cannot preserve affinity, for example
if the affinity ODR went down, then the IHS randomly picks another ODR. This new ODR will either route the request and
adopt the session, or it will try to find an ODR which can route the request, and that ODR will adopt the session. This log
message is used to identify the original ODR which hosted the session, and the new ODR which is adopting the session.
In-session HTTP requests contain a session cookie (or session ID encoded in the URL) which
identify not only the session to the application, but the server to the On-Demand Router.
This entry indicates that a request contained a session ID, but all attempts to preserve
affinity to the server hosting the session failed.
The selected cluster.
This type of cluster is defined as the collection of servers that are both running the module
and are a member of a physical cluster. If the physical cluster is null, then this type of
cluster contains all servers that are running the module. If the module is deployed to multiple
physical clusters, then this cluster will contain servers from all physical clusters that are
running the module.
An HTTP request was dispatched (i.e. proxied) to a backend application server.
An HTTP request could not be sent to previously selected server, so try another.
An HTTP request is being redirected to another URL.
Protocols used for this request. Client, inbound, and outbound (mapped).
An HTTP 404 error is returned with various levels of information in the 'reason' depending upon the level:
0: Disabled
1: Give a concise reason for the failure.
2: Give a reason for the failure, plus a ODC tree view (or reference to a previously-logged ODC tree view) for the web module.
3: Give a reason for the failure, plus a target.xml tree (or reference to a previously-logged tree).
4..11: Undefined.
12: Equivalent to 2, but always produce the ODC tree view for the web module (no references).
13: Equivalent to 3, but always produce a target.xml tree (no references).
An HTTP 503 error is returned with various levels of information in the 'reason' depending upon the level:
0: Disabled
1: Give a concise reason for the failure.
2: Give a reason for the failure, plus a ODC tree view (or reference to a previously-logged ODC tree view) for the web module.
3: Give a reason for the failure, plus a target.xml tree (or reference to a previously-logged tree).
4..11: Undefined.
12: Equivalent to 2, but always produce the ODC tree view for the web module (no references).
13: Equivalent to 3, but always produce a target.xml tree (no references).
A URI could not be found for the given application edition.
Proxy exceptions can occur during request/response processing (e.g. a link goes down). These can be
stored for the request and produced when the response has been processed (regardless of the response).
;sr com.ibm.ws.trace.TraceXml xpt 7bundleresource://131.fwk-569085495:6/META-INF/trace.xmlz
This group provides tracing for all ODC events.
An ODC node property change event was ignored for one of the following reasons:
(1) the new value is the same as the old value;
(2) the priority of the old value is higher than the priority of the new value.
Name of the ODC transaction making tree changes
An ODC node is added or deleted
An ODC edge is added or deleted
An ODC node property is changed
Contains records used by the trace facility
The record that is written to beginning of each file.
The path of the file.
The fully qualified process name of the form: cell/node/process
This record is written to the beginning of each block of trace information to identify the
writer of the following records.
A count to uniquely identify the instance of the following trace records.
xsq ~ t 7bundleresource://131.fwk-569085495:7/META-INF/trace.xmlz
The replayer input dump is for IBM development use only.
The replayer output dump is for IBM development use only.
ARFM (Autonomic Request Flow Manager) dynamically regulates the flow of HTTP requests, SIP messages, IIOP calls, and JMS MDB messages.
The ARFM controller receives statistics from various sources. Based upon
those statistics and upon service policy configuration, the ARFM controller
then controls how traffic is processed by the ARFM gateways. The ARFM gateways
are in the ODR process for HTTP and SIP traffic, and in the application server
process for Iz IOP and JMS traffic.
The name of this flow.
The number of virtual seats allocated.
The first tier work factor (alpha).
The utility value.
The average queue length.
Average number executing.
z Average service time.
Average response time.
Average wait time in the queue.
The maximum of maxExec and the average concurrency allocation, in physical seats.
The message arrival rate, in msgs/sec, averaged over the last control cycle.
The admission rate of messages that initiate logical dialogs.
The rate of messages that (a) wez re enqueued during the reported interval,
(b) are not retransmissions of earlier messages, and (c) initiate a logical dialog.
The rate of requests dispatched from the queue to a server.
The rate of message completions.
The rate of dropped messages.
The service time variance.
A QStat record contains statistics for a particular gateway, where a gateway is identified
by a (protocolSuite,ODR,deploymentTarget) tuple. For example, there is a gatewaz y for
HTTP traffic flowing through ODR cell1/node1/odr1 to cluster cell1/cluster1.
Unique identifier for the ARFM gateway. The format is protocol:deploymentTarget:cell_node_odr.
For HTTP, 'protocol' is the empty string.
Average queue length for this flow.
Average number executing.
Average service time of requests that completed during the measurement interval.
Average response time of requests that completed during the measurement interval.
Average wait time in the queue for requests dispatched during the measurement interval.
Maximum number executing during the measurement interval.
The number of requests that arrived during the measurement interval.
z The number admitted is this value less the number not admitted
(see 'dropped' field for how to count those).
The number of messages that (a) were enqueued during the reported interval,
(b) are not retransmissions of earlier messages, and (c) initiate a logical dialog.
The number of requests dispatched from the queue to server during the measurement interval.
The number of requests whose execution completed during the measurement interval.
The number of requests that (1) arrived during the measurement interval and (2) were not immediately dispatched or dropped.
The longest successful service time seen during the most recent high water mark period.
The sum, over each millisecond in the measurement interval,
of the number of requests that were estimated to be stuck executing at the start of the millisecond.
The number of requests that completed during the reported interval and had a response time above the service class threshold.
The number ofz requests dropped from any reason during the measurement interval.
The number of requests that were initially accepted into the queue and then, at some time during the reported interval, ejected from the queue.
The number of requests that completed during the measurement interval due to service timeout.
The number of requests that completed during the measurement interval with an error.
The sum, over the requests whose execution completed during the measurement interval, of the square of the request's service time. The sum is in units of milliseconds. Divide bz y serviced to get average.
Describes the computational power available in a given target cell.
Node name.
Node speed.
Background speed.
Describes the computational power assigned to each Dynamic Cluster by APC.
Cluster name.
Cluster power.
Describes the utility function generated by ARFM for each dynamic cluster.
Cluster name.
Maximum allocation requested.
The speed request in units of work/sec.
A connection failure can occur when the ODR cannot connect to a
back-end server.
z
z
z
z
In-session HTTP requests contain a session cookie (or session ID encoded in the URL) which
identify not only the sessiz on to the application, but the server to the On-Demand Router.
This entry indicates that a request contained a session ID, that the target server has been located,
and that affinity to it may be preserved.
When a session is established through an IBM HTTP Server (IHS) and an On-Demand Router (ODR) to an application server in
an environment where the IHS fronts multiple cells, then for in-session requests, it is necessary to instruct the IHS
to route to the same ODR -- i.e., the IHS must preserve ODR affinity. If the IHS cannot preserve affinity, for example
if the affinity ODR went down, then the IHS randomly picks another ODR. This new ODR will either route the request and
adopt the session, or it will try to find an ODR which can route the request, and that ODR will adopt the session. This log
message is used to identify the original ODR which hosted the session, and the new ODR which is adopting the session.
z
In-session HTTP requests contain a session cookie (or session ID encoded in the URL) which
identify not only the session to the application, but the server to the On-Demand Router.
This entry indicates that a request contained a session ID, but all attempts to preserve
affinity to the server hosting the session failed.
The selected cluster.
This type of cluster is defined as the collection of servers that are both running the module
and are a member of a physical cluster. If the physical cluster is null, then this type of
cluster contains all servers that are running the module. If the module is deployed to multiple
physical clusters, then this cluster will contain servers from all physical clusters that are
running the module.
z
z
An HTTP request was dispatched (i.e. proxied) to a backend application server.
An HTTP request could not be sent to previously selected server, so try another.
An HTTP request is being redirected to another URL.
Protocols used for this request. Client, inbound, and outbound (mapped).
An HTTP 404 error is returned with various levels of information in the 'reason' depending upon the level:
0: Disabled
1: Give a concise reason for the failure.
2: Give a reason for the failure, plus a ODC tree view (or reference to a previously-logged ODC tree view) for the web module.
3: Give a reason for the failure, plus a target.xml tree (or reference to a previously-logged tree).
4..11: Undefined.
12: Equivalent to 2, but always produce the ODC tree view for the web module (no references).
13: Equivalent to 3, but always produce a target.xml tree (no references).
An HTTP 503 error is returned with various levels of information in the 'reason' depending upon the level:
0: Disabled
1: Give a concise reason for the failure.
2: Give a reason for the failure, plus a ODC tree view (or reference to a previously-logged ODC tree view) for the web module.
3: Give a reason for the failure, plus a target.xml tree (or reference to a previously-logged tree).
4..11: Undefined.
12: Equivalent to 2, but always produce the ODC tree view for the web module (no references).
13: Equivalent to 3, but always produce a target.xml tree (no references).
A URI could not be found for the given application edition.
Proxy exceptions can occur during request/response processing (e.g. a link goes down). These can be
stored for the request and produced when the response has been processed (regardless of the response).
z
xt ctgCell01/ctgCellManager01/dmgrt arfmt ODCEventt ODCt httpt networkt 1/cell/ctgCell01/node/ctgCellManager01/server/dmgrt server:statet server:server.maintenancemodet addNodet -/cell/ctgCell01/cluster/ctgCellManager01:dmgrt ./cell/ctgCell01/node/ctgNode01/server/MXServert */cell/ctgCell01/cluster/ctgNode01:MXServert //cell/ctgCell01/node/ctgNode01/server/nodeagentt +/cell/ctgCell01/cluster/ctgNode01:nodeagentt 0/cell/ctgCell01/node/ctgNode01/server/webserver1t ,/cell/ctgCell01/cluster/ctgNode01:webserver1t
deleteNodet #/cell/ctgCell01/application/commsvct '/cell/ctgCell01/application/ibmasyncrspt addEdget A/cell/ctgCell01/application/ibmasyncrsp/webModule/ibmasyncrsp.wart #/cell/ctgCell01/application/isclitet 9/cell/ctgCell01/application/isclite/webModule/isclite.wart A/cell/ctgCell01/application/isclite/webModule/adminredirector.wart 6/cell/ctgCell01/application/isclite/webModule/iehs.wart A/cell/ctgCell01/application/isclite/webModule/ISCAdminPortlet.wart