IBM WebSphere ODR - How to Handle Out Of Memory with ODR

Overview

IBM Websphere On Demand Router (or) ODR can prevent the application JVM from running out of memory due to the large number of connections that can acquire in the ODR - On Demand Router, the ODR automatically starts rejecting requests and thus closing connections, when the heap utilization exceeds a maximum threshold.

Prerequisite

WebSphere application server profile with application deployed.

 

Procedure

You can create cell-level custom properties to prevent the on demand router (ODR) from running out of memory when the number of concurrent requests sent to the ODR increases.

To configure a percentage value that determines at what amount of heap usage the ODR rejects requests

  • In the administrative console, select System administration > Cell > Custom properties > New.
  • Specify the name of the custom property as ODR.heapUsage.max.
  • Specify a value for the custom property.
  • The default value is 90. To disable this feature, set the value to 100.
  • If heap usage exceeds 90%, the ODR rejects any incoming request and a 503 error code is returned
  • Click Save, Review & Apply changes.

You can also set the property to configure the type of error code that is returned when a request is received and the heap usage exceeds the maximum threshold.

  • In the administrative console, select System administration > Cell > Custom properties > New.
  • Specify the name of the custom property as ODR.heapUsage.errorCode.
  • Specify a value for the custom property. The default value is 503.
  • Click Save, Review & Apply changes.

 

Follow me on Linkedin My Profile
Follow DevopsJunction onFacebook orTwitter
For more practical videos and tutorials. Subscribe to our channel

Buy Me a Coffee at ko-fi.com

Signup for Exclusive "Subscriber-only" Content

Loading