Claus Ibsen created CAMEL-25901:
-----------------------------------
Summary: camel-jms - docs: a request-reply example in Java, XML
and YAML, and the AI tools say to use InOut instead of setting JMSReplyTo
Key: CAMEL-25901
URL: https://issues.apache.org/jira/browse/CAMEL-25901
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-jms
Reporter: Claus Ibsen
Fix For: 4.24.0
A JMS request-reply step of the benchmark (a route calls a stock service over a
queue and uses its reply) 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
(7), or direct: instead of the queue (3).
Two things led there:
* The docs section "Request-reply over JMS" opens with a table of reply-queue
options (temporary, shared, exclusive), and its only example is Java
(to(ExchangePattern.InOut, ...)). The 4 runs that read it all set a reply queue
by hand. camel_catalog_sample jms returned no request-reply example: the first
two were "receive from a queue" and "filter a topic".
* The header check answered a route that read ${header.CamelJmsReplyTo} with
"did you mean JMSReplyTo?", and the model then set JMSReplyTo itself.
Proposal:
* 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 the
InOut pattern 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 the replyTo option and a
JMSReplyTo header are not set for this. It is the second jms sample now. The
filter example moves to "Routing JMS messages". The section "Request-reply over
JMS" points to the example and says the same.
* The header check: for a header name with "Reply" that is not set (such as
CamelJmsReplyTo), the hint says to send with pattern: InOut on the to:, because
Camel sets JMSReplyTo and waits for the reply. It no longer says "did you mean
JMSReplyTo?".
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
