-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Description
Hello,
I notice (not sure if it is an issue or not) at the server map level : I give you more details
In this example, we could see that the transaction duration between the component A and the component B was 32.6 seconds
And we could see that the user transaction has been rejected due to a read timeout (60 seconds) : between the user and the component A (the transaction duration was 60.8 seconds)
I was thinking that there is a technical issue at the level of the component A, but I discovered (based on the call tree) that the issue was at the level of the IO pool of the component B.
My question is :
Why the transaction duration between the component A and the component B was 32.6 seconds instead of 60,882 (the total value of the gap duration and the execution duration) ? it is an issue or it works as designed ?
Thanks.