You can use on demand router (ODR) custom properties to change the behavior of your ODR. For example, you can change the error code that the ODR returns when messages are rejected because of processor or memory overload.
To set a custom property on the ODR, complete the following steps:
Use the http.log.history custom property to specify the number of history server log files. The server log files are the ODR custom log files, as well as the proxy.log, local.log, and cache.log files. Without this custom property, you have one history file for the server log files. Setting this custom property does not affect the custom logs that are already initialized.
Scope | ODR or ODR cluster |
---|---|
Value | Any positive integer greater than 0 |
Default | 1 |
Use the http.log.maxSize custom property to specify the maximum log size in megabytes (MB). A value of UNLIMITED indicates unlimited. As with the http.log.history custom property, the http.log.maxSize custom property applies to the ODR custom log files, as well as the proxy.log, local.log, and cache.log files.
Scope | ODR or ODR cluster |
---|---|
Value | Any positive integer greater than 0 |
Default | 25 MB |
Use the ODR.heapUsage.max custom property to configure a percentage value that determines at what amount of heap usage the ODR rejects requests. If heap usage exceeds 90%, the ODR rejects any incoming request and a 503 error code is returned.
Scope | Cell |
---|---|
Value | Percentage |
Default | 90% |
Use the ODR.heapUsage.algorithm custom property to configure when heap usage is calculated. If you set the value to globalGC, the amount of heap usage is calculated only immediately after a global garbage collection cycle. If you set the value to request, the amount of heap usage is calculated with each request.
Scope | Cell |
---|---|
Value | Algorithm |
Default | globalGC |
Use the ODR.heapUsage.errorCode custom property to configure the type of error code that is returned when a request is received and the heap usage exceeds the maximum threshold.
Scope | Cell |
---|---|
Value | Integer |
Default | 503 |
Use the http.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when an HTTP message over TCP or SSL is rejected due to processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Scope | On demand router |
---|---|
Value | Integer |
Default | 503 |
Use the sip.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when a Session Initiation Protocol (SIP) message over Transmission Control Protocol (TCP) or Secure Sockets Layer (SSL) is rejected because of processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Scope | On demand router |
---|---|
Value | Integer |
Default | 503 |
Use the sipu.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when a Session Initiation Protocol (SIP) message over User Datagram Protocol (UDP) is rejected due to processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Scope | On demand router |
---|---|
Value | Integer |
Default | 503 |
Use the http.partialResponseBodyBufferSize custom property to disable the ODR from buffering the size of the response payload when you perform a rollout on an application edition. Set the http.partialResponseBodyBufferSize custom property to a value of 0.
Scope | On demand router |
---|---|
Value | Integer |
Default | 0 |
Use the ODCLeftGroupDelay =0 system property set to allow no delay for on demand configuration detection of down servers during failover when servers become unavailable.
From the administrative console, select Servers > On Demand Routers >on_demand_router > Java and Process Management > Process Definition > Java Virtual Machine.
Use the ODRtraceRouteHeader =0 system property on the ODR, and it will add a response header with the route that the request took.
From the administrative console, select Servers > On Demand Routers >on_demand_router > Java and Process Management > Process Definition > Java Virtual Machine.
For example, -DODR.traceRouteHeader=TraceRoute adds a response header with the name TraceRoute to each request. The value of this response header is the path that the request took.