You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2021/04/05 05:56:00 UTC

[jira] [Updated] (AMQ-7427) Durable subscriber

     [ https://issues.apache.org/jira/browse/AMQ-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated AMQ-7427:
--------------------------------------
    Fix Version/s:     (was: 5.15.15)
                   5.15.16

> Durable subscriber
> ------------------
>
>                 Key: AMQ-7427
>                 URL: https://issues.apache.org/jira/browse/AMQ-7427
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.14.0
>            Reporter: Timothy Kim
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.16.2, 5.15.16
>
>
> I am using REST protocol to create a durable consumer.  And according to the online help,  a given clientid in a url  is to be used always. But when I checked the console, a new clientid is created instead, e.g. ID:TIMK10-56032-1582923785025-3:1. Is this a bug or as designed?
>  
> Online help ([https://activemq.apache.org/rest])
> -----------------
> Since 5.2.0 you can use {{clientId}} parameter to avoid storing actual JMS consumer in the request session. When using this approach, you don't need to keep sessions alive between requests, you just need to use the same {{clientId}} every time.
> {{[http://localhost:8161/api/message/test?type=queue&clientId=consumerA]}}
>   
>  Every such call will use the same JMS consumer and deliver messages send to it by the broker.
> -------------------
>  
> Thanks.
> Tim
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)