ASF GitHub Bot logged work on ARTEMIS-2680:

                Author: ASF GitHub Bot
            Created on: 25/Mar/20 14:01
            Start Date: 25/Mar/20 14:01
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on issue #3047: ARTEMIS-2680 use q 
name for addr if none specified via config
URL: https://github.com/apache/activemq-artemis/pull/3047#issuecomment-603856438
   @michaelandrepearce, currently if you add a `CoreQueueConfiguration` object 
with no address to `Configuration` and start the broker the queue will fail to 
load with a WARN message. However, if you invoke one of the overloaded 
`createQueue` methods with effectively no address the queue will be created 
using the queue's name as the address name. The behavior from `createQueue` 
seems OK to me so I think using `CoreQueueConfiguration` should work the same.
   To be clear, the use-case here is an embedded broker without XML 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 409533)
    Time Spent: 50m  (was: 40m)

> Use queue name for address if none specified via configuration
> --------------------------------------------------------------
>                 Key: ARTEMIS-2680
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2680
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 50m
>  Remaining Estimate: 0h
> If 
> {{org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl#createQueue()}}
>  is invoked with an effectively {{null}} address name then the queue name 
> will be used for the address. This is not true of queues created via 
> {{org.apache.activemq.artemis.core.config.CoreQueueConfiguration}}, but it 
> should be.

This message was sent by Atlassian Jira

Reply via email to