Claus Ibsen created CAMEL-23554:
-----------------------------------

             Summary: RuntimeEndpointRegistry does not track out hits for InOut 
consumer endpoints
                 Key: CAMEL-23554
                 URL: https://issues.apache.org/jira/browse/CAMEL-23554
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
            Reporter: Claus Ibsen


InOut consumers like platform-http receive a request and always send a response 
back to the client. The RuntimeEndpointRegistry tracks the inbound request as 
an "in" hit (via ExchangeCreatedEvent), but the outbound reply is never 
recorded as an "out" hit.

This means the TUI endpoint tab, flow diagram, and sparkline charts only show 
incoming request counters for HTTP server endpoints, even though they always 
send a response. The same gap affects the camel get endpoint CLI output and JMX 
statistics.

The fix extends DefaultRuntimeEndpointRegistry to also listen for 
ExchangeCompletedEvent and ExchangeFailedEvent. When an InOut exchange 
completes, an "out" hit is recorded on the consumer's fromEndpoint. The 
isOutCapable() check ensures InOnly consumers (timer, file, etc.) are not 
affected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to