In a distributed WSO2 API Manager setup, throttling functionality was not working correctly when one or more traffic manager nodes were unavailable. Specifically, when one traffic manager node could not establish a connection while another was still active, event duplication led to threads becoming stuck, causing throttling failures.
Use the broker connection timeout property to introduce a waiting timeout for the broker pooled connection establishment
Impact
The process of establishing a broker connection will continue trying until the specified timeout is reached. If a timeout is defined in the broker's URL properties, that value will be used. Otherwise, the connection attempt will default to a 120-second timeout if no specific connect timeout is provided.
Purpose
In a distributed WSO2 API Manager setup, throttling functionality was not working correctly when one or more traffic manager nodes were unavailable. Specifically, when one traffic manager node could not establish a connection while another was still active, event duplication led to threads becoming stuck, causing throttling failures.
Fix
Use the broker connection timeout property to introduce a waiting timeout for the broker pooled connection establishment
Impact
The process of establishing a broker connection will continue trying until the specified timeout is reached. If a timeout is defined in the broker's URL properties, that value will be used. Otherwise, the connection attempt will default to a 120-second timeout if no specific connect timeout is provided.