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

ASF GitHub Bot logged work on AMQ-7376:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Feb/20 05:03
            Start Date: 07/Feb/20 05:03
    Worklog Time Spent: 10m 
      Work Description: jbonofre commented on issue #428: AMQ-7376 - Use 
correct type for collections retrieval
URL: https://github.com/apache/activemq/pull/428#issuecomment-583235738
 
 
   It seems that this change is causing issue at least in Spring support. I'm 
investigating.
 
----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 383395)
    Time Spent: 20m  (was: 10m)

> Use correct type for collections retrieval
> ------------------------------------------
>
>                 Key: AMQ-7376
>                 URL: https://issues.apache.org/jira/browse/AMQ-7376
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Colm O hEigeartaigh
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.16.0, 5.15.12
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There are a few instances where we are using the wrong (object) type with 
> collections:
>  * Queue - browserDispatches.remove(sub) will always fail as the list holds 
> different objects
>  * KahaDbStore - storeCache.get(convert(activeMQDestination)) will always 
> fail as the destination needs to be converted to a key first
>  * MQTTProtocolConverter - activeMQDestinationMap.get(command.topicName()) - 
> should be using toString() here instead.



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

Reply via email to