IT19531: DATAPOWER ODR PROCESSING IS NOT WORKING CORRECTLY FOR CERTAIN DYNAMIC-BACKEND SCENARIOS
Fixes are available
Closed as program error.
When using an API collective member (which is running on node js for micro service) as part of the API connect platform. In this case, the symptom was receiving HTTP 503 errors when ODR tries connecting to api collective backend. The 503 error is because ODR incorrectly thinks the maximum number of connections of WAS was reached.
1. Use a log target set with an event target to call CLI to reset ODR object. The event target will monitor for the "outstanding request count" when it gets close to the failure event, "outstanding requests 99999 exceeded maximum 99999 connections". 2. Create a MPGW with type "Static Backend" set to handle the call (http://ODR-DYN)to the odrlib. client <---> DP/MPGW with DynamicBE that calls to loopback <---> MPGW with StaticBE that calls odrlib <---> BE(Backend).
ODR problems with memory leak and getting HTTP 503 errors when ODR connects to an API collective backend.
Redirect and Error URL Open cases now work with dynamic backends using session affinity Fix is available in 18.104.22.168, 22.214.171.124 and 126.96.36.199 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels