You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to call the just “/” or invalid API context.
When there is network latency the issue is reproducing and the below logs are getting printed.
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
No response
Relevant Log Output
WARN {org.apache.synapse.transport.passthru.SourceHandler} - STATE_DESCRIPTION = Socket Timeout occurred after accepting the request headers and the request body, INTERNAL_STATE = REQUEST_DONE, DIRECTION = REQUEST, CAUSE_OF_ERROR = Connection between the client and the WSO2 server timeouts, HTTP_URL = /, HTTP_METHOD = GET, SOCKET_TIMEOUT = 180000, CLIENT_ADDRESS = /********:**, CORRELATION_ID = *********, CONNECTION = http-incoming-1876, Could not get a PassThroughMessageProcessor thread to process the request message. The primary worker pool is exhausted.
INFO {org.apache.synapse.transport.passthru.SourceHandler} - Writer null when calling informWriterError
WARN {org.apache.synapse.transport.passthru.SourceHandler} - STATE_DESCRIPTION = Socket Timeout occurred after accepting the request headers and the request body, INTERNAL_STATE = REQUEST_DONE, DIRECTION = REQUEST, CAUSE_OF_ERROR = Connection between the client and the WSO2 server timeouts, HTTP_URL = /test/1.0.0/new?responsave=****, HTTP_METHOD = GET, SOCKET_TIMEOUT = 180000, CLIENT_ADDRESS = /******:***, CORRELATION_ID = **********, CONNECTION = http-incoming-1877, Could not get a PassThroughMessageProcessor thread to process the request message. The primary worker pool is exhausted.
INFO {org.apache.synapse.transport.passthru.SourceHandler} - Writer null when calling informWriterError
Related Issues
No response
Suggested Labels
APIM 4.2.0
The text was updated successfully, but these errors were encountered:
Description
The APIM server returns a timeout error when calling the non-existing context recursively during the tracing or telemetry enabled.
Steps to Reproduce
When there is network latency the issue is reproducing and the below logs are getting printed.
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
No response
Relevant Log Output
Related Issues
No response
Suggested Labels
APIM 4.2.0
The text was updated successfully, but these errors were encountered: