[
https://issues.apache.org/jira/browse/CAMEL-22952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-22952:
--------------------------------
Summary: Camel JBang cmd receive - does not support when using stub (was:
Camel JBang cmd receive is broken)
> Camel JBang cmd receive - does not support when using stub
> ----------------------------------------------------------
>
> Key: CAMEL-22952
> URL: https://issues.apache.org/jira/browse/CAMEL-22952
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.17.0
> Reporter: Christoph Deppisch
> Priority: Minor
> Fix For: 4.18.0
>
>
> I am observing a regression in the Camel JBang receive command. The command
> should receive messages from an existing stub endpoint in a running Camel
> integration.
> This seems to be broken as no messages are received at all
> Given the following Camel integration
>
> {noformat}
> - from:
> uri: "direct:echo"
> steps:
> - wireTap:
> uri: "log:info"
> - to:
> uri: "jms:queue:foo"{noformat}
> When running this with stub JMS endpoint like this
> {noformat}
> camel run my-route.yaml --stub=jms{noformat}
> I am expecting to receive messages from the stub endpoint with
> {noformat}
> camel cmd receive --endpoint=jms my-route{noformat}
> I am sending messages to the route with
> {noformat}
> camel cmd send events --body=Hello{noformat}
> This has been working with Camel 4.16.0 but since 4.17.0 no messages are
> received.
> I can see the stub being active and holding messages with
> {noformat}
> camel cmd stub --browse{noformat}
> This shows me the messages that I have sent to the route but _*cmd receive*_
> does not
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
