Description
Blocking receive actions (e.g., waiting for an HTTP request on a server endpoint) produce no log output when they start waiting. If the receive eventually times out, the only indication is the timeout error — there is no earlier log line showing what the test was blocked on or when it started waiting.
Current Behavior
No log output between starting a receive action and the timeout error:
<silence for 2 minutes>
TEST FAILED ... Action timeout after 120000 milliseconds. Failed to receive message on endpoint: 'jiraServer.inbound'
Expected Behavior
Receive actions should log when they start waiting, e.g.:
Waiting to receive message on endpoint: 'jiraServer.inbound' (timeout: 120000ms)
This makes it immediately clear what the test is blocked on, especially when combined with other log lines from preceding actions.
Additional Context
Reported in apache/camel-kamelets#2867. The lack of logging made it difficult to diagnose where the test was stuck.
Description
Blocking receive actions (e.g., waiting for an HTTP request on a server endpoint) produce no log output when they start waiting. If the receive eventually times out, the only indication is the timeout error — there is no earlier log line showing what the test was blocked on or when it started waiting.
Current Behavior
No log output between starting a receive action and the timeout error:
Expected Behavior
Receive actions should log when they start waiting, e.g.:
This makes it immediately clear what the test is blocked on, especially when combined with other log lines from preceding actions.
Additional Context
Reported in apache/camel-kamelets#2867. The lack of logging made it difficult to diagnose where the test was stuck.