davsclaus opened a new pull request, #28211: URL: https://github.com/apache/camel/pull/28211
https://issues.apache.org/jira/browse/CAMEL-25901 A JMS request-reply step of the benchmark failed 12 of 12 times on two nights. In 10 runs the request-reply was wired wrong: one-way with a `replyTo` or `JMSReplyTo` set by hand, or `direct:` instead of the queue. The section "Request-reply over JMS" opens with the reply-queue option table, and its only example is Java. `camel_catalog_sample jms` had no request-reply example among the first two. And the header check answered `${header.CamelJmsReplyTo}` with "did you mean JMSReplyTo?", so the model set it by hand. ## Changes - **jms docs:** a new example, "Sending a request and waiting for the reply", in Java, XML and YAML, right after the first example. - The caller sends with `pattern: InOut` and `variableReceive`. The service route consumes the queue, and the body at the end of its route is the reply. - The text says that Camel creates a temporary reply queue and sets `JMSReplyTo`, so `replyTo` and `JMSReplyTo` are not set for this. - It is now the second jms sample of `camel_catalog_sample`. The filter example moves to its own section, "Routing JMS messages". - "Request-reply over JMS" points to the example and says the same. The catalog copy of the page is the same as the page. - **Header check:** a header name with `Reply` that is not set (such as `CamelJmsReplyTo`) gets the request-reply hint: send with `pattern: InOut` on the `to:`, and Camel sets `JMSReplyTo` and waits for the reply. It no longer says "did you mean JMSReplyTo?". The YAML example validates with `camel validate yaml`. The jms example of the benchmark uses the same shape (InOut and `variableReceive`), and its reference solution passes against Artemis. Tests: `SourceValidatorEndpointTest.aReplyHeaderGetsTheRequestReplyHint`. camel-jbang-core 2401 + 237 pass. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
