[ 
https://issues.apache.org/jira/browse/ARTEMIS-5911?focusedWorklogId=1006980&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1006980
 ]

ASF GitHub Bot logged work on ARTEMIS-5911:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Feb/26 22:53
            Start Date: 24/Feb/26 22:53
    Worklog Time Spent: 10m 
      Work Description: tabish121 opened a new pull request, #6249:
URL: https://github.com/apache/artemis/pull/6249

   …tion
   
   When parsing the Core federation XML elements we need to ensure that AMQP 
broker connections with federation configuration does not get picked up as that 
creates empty configuration entries in the broker configuration.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 1006980)
    Remaining Estimate: 0h
            Time Spent: 10m

> AMQP Federation configuration triggers empty Core federation entries
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-5911
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5911
>             Project: Artemis
>          Issue Type: Bug
>          Components: AMQP, Federation
>    Affects Versions: 2.51.0
>            Reporter: Timothy A. Bish
>            Assignee: Timothy A. Bish
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.52.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When reading configuration XML if there is an AMQP federation configuration 
> in a broker connection it triggers the core federation parser to create an 
> empty federation configuration entry. This does not create a Core federation 
> as there are no upstream or downstream elements it does make it confusing 
> that these entries show up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to