of this e-mail is really necessary.
>
>
>
>
> Von: "Robbie Gemmell"
> An:users@activemq.apache.org
> Datum:09.09.2024 18:42
> Betreff:[Ext] Re: Re: Re: Artemis ClientID and shared topics
> --
&g
:"Robbie Gemmell"
An: users@activemq.apache.org
Datum: 09.09.2024 18:42
Betreff:[Ext] Re: Re: Re: Artemis ClientID and shared topics
JMS 1 says that the named durable subscriptions are ClientID-scoped, you
needed a ClientID to use a named durable subscription (in pra
HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786
> Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO
>
> P Please check whether a printout of this e-mail is really necessary.
>
>
>
>
> Von:"Robbie Gemmell"
> An:users@acti
egards
Herbert
Von:"Robbie Gemmell"
An: users@activemq.apache.org
Datum: 09.09.2024 12:16
Betreff: [Ext] Re: Re: Artemis ClientID and shared topics
JMS 2 essentially outlined that shared named subscriptions on Connections
with a ClientID are still ClientID-scoped (i.
> What has the clientID to do with shared topics anyway?
The client ID, at least in part, forms the identity of the subscription.
This is noted in section 8.3.2 of the JMS 2 specification which states:
A shared non-durable subscription is identified by a name specified by the
client and by th
