Incorrect reason code -5 returned for Max Duration Timeout in Route Assertion

Products

• CA API Gateway

Issue/Introduction

When testing the Max Duration Timeout feature in the Route via HTTP(S) assertion on Layer7 API Gateway 11.2, the variable ${httpRouting.reasonCode} may return a value of -5 instead of the expected -6 documented in TechDocs. This typically occurs when the gateway is not operating in the default Buffering Mode or due to a known code defect.

Environment

• Product: Layer7 API Gateway
• Release: 11.2, 11.2.1

Cause

The behavior of the reason code depends on the Response Message Handling configuration of the routing assertion:

1. Buffering Mode (Default): The assertion should set httpRouting.reasonCode = -6.
2. Streaming Mode: The response streaming is handled by the SoapMessageProcessingServlet. If the timeout is reached here, the servlet kills the stream and sets a service status of 600, but the routing assertion may return a different code based on the backend's initial response.

A code defect (DE673786) was identified where the incorrect code was returned even when the timeout was triggered.

Resolution

This issue is Targeted to be fixed in release 11.2.2 and 12.0.

Once the fix is GA, the resolution is as follows: Fixed in release 11.2.2, 12.0 and higher. See Download Broadcom products and software for steps to download this release.

Current Workaround/Clarification:

1. Verify if the assertion is set to Buffer or Stream under the Response Message Handling tab.
2. If using Buffering Mode, ensure the "Max Duration Timeout" is set correctly. The gateway should log Message was not processed: Assertion Falsified (600).
3. In Streaming Mode, expect a 200 OK with a truncated body if the timeout occurs after the headers are sent, as the ResponseKillerValve will terminate the stream.

Recommend subscribing to this article to be updated on the fix status (Reference: How to subscribe to Knowledge Base articles).

Additional Information

• TechDocs: Using Max Duration Timeout and Response Message Handling
• To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.