Fix SO timeout log issue when the worker pool is exhausted. #2081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix SO timeout log issue when the worker pool is exhausted. Change SO timeout log structure.
Define new logs to identify secondary worker pool exhausting scenarios (by defining new max queueing time for that as well + at SO timeout) Change the implementation of max queueing time since it's error-prone with a new thread pool.
Improve the logs to indicate secondary passthrough pool is exhausted when all threads are busy.
Fixes: wso2/api-manager#1923
Add discard logic to clientWorker when secondary pool is not available
Move thread state to the relevant worker thread itself
Done a fix to move the thread state to the relevant worker thread itself rather than keeping it in the connection.
Fixes: wso2/api-manager#1923
Related to: https://github.com/wso2-support/wso2-synapse/pull/2135
Purpose
Goals
Approach
User stories
Release note
Documentation
Training
Certification
Marketing
Automation tests
Security checks
Samples
Related PRs
Migrations (if applicable)
Test environment
Learning