Marco Bungart created CAMEL-19591:
-------------------------------------
Summary: Artemis JMS Client: client Id not set and not respected
for subscriptions
Key: CAMEL-19591
URL: https://issues.apache.org/jira/browse/CAMEL-19591
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 3.21.0
Environment: - Java:
{code:sh}
openjdk version "17.0.7" 2023-04-18
OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode, sharing)
{code}
- Camel: {{3.21.0}} (but I have observed the issue also on {{3.18.x}} and
{{3.20.x}} I have not checked older versions)
- Artemis-client: {{2.29.0}} (but I have observed the issue also on version
{{{}2.28.0{}}}, I have not checked older versions)
- Artemis-broker image:
{{quay.io/artemiscloud/activemq-artemis-broker:1.0.19}} (which corresponds to
Artemis {{{}2.29.0{}}}, but I have observed the issue also on {{{}2.28.0{}}}, I
have not checked older versions)
Reporter: Marco Bungart
Attachments: connections.png, queues.png
Whe using `to(jms(...)....clientId("some-client-id"))...`, in combination with
the artemis jms client, the `clientId` is neither sent nor considered for
durable subscriptions.
Reproducer:
- Checkout [https://github.com/turing85/camel-jms:]
{code:sh}
git clone https://github.com/turing85/camel-jms.git
cd camel-jms
{code}
- Start artemis:
{code:sh}
docker-compose --file local-deployment/docker-compose.yml up --detach
{code}
- Build the application:
{code:sh}
./mvnw clean package
{code}
- Start the application:
{code:sh}
java -jar target/camel-jms-1.0-SNAPSHOT-executable-jar.jar
{code}
- Observe that the application is sending and receiving messages
- Access the Artemis web ui at [http://localhost:8161/console], log in with
any credentials (Artemis is running in dev mode; the credentials will not be
verified)
- Switch to the "Connections"-tab, observe that the client has no clientId set:
!connections.png!
- Navigate to broker -> addresses -> numbers -> queues -> multicast, observe
that the queue is named "receiver-subscription", which is the subscription name
configured. However, it should be a combination of the client id (which is set
to "receiver-client") and the subscription name:
!queues.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
