JMS Uniform Distributed Queue Member has Inconsistent Consumer Count with API Gateway Axway Acting As Consumer (Doc ID 3055279.1)

Last updated on OCTOBER 25, 2024

Applies to:

Symptoms

JMS Uniform Distributed Queue Member has Inconsistent Consumer Count with API Gateway Axway acting as Consumer.

In a clustered environment, the JMS Uniform Distributed Queue (UDQ) members exhibit an inconsistent consumer count. Specifically, the first member of the UDQ consistently receives fewer consumers than expected, while the second and third members receive the correct number. The issue persists despite restarting the managed servers, and it's observed that the consumer count for the first member fluctuates between 0, 1, and 2.

Axway, the API Gateway acting as a consumer on the UDQ, has three nodes, each targeting the individual UDQ members. The expectation is that each member should receive three consumers from the corresponding Axway nodes.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.