[jira] [Commented] (AMQ-3655) No information of destinations is present on web console or jconsole even my activemq_msgs, have lots of destinations when broker starts up

["Timothy Bish (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181423#comment-13181423 ] 

Timothy Bish commented on AMQ-3655:
-----------------------------------

Have you tested this against the latest 5.6-SNAPSHOT, I think there were already some fixes in this area.
                
> No information of destinations is present on web console or jconsole even my activemq_msgs, have lots of destinations when broker starts up
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3655
>                 URL: https://issues.apache.org/jira/browse/AMQ-3655
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>              Labels: jdbcstorage
>             Fix For: 5.6.0
>
>
> I have just noted that there is no information about existing destinations on web console or jconsole after my broker starts up.These destinations exist on my message table activemq_msgs and they are present again when some producers or consumers are active.
> I'm sure this works well on 5.2 because I had used this to inspect my destinations before 2 years ago.
> I also check the source code of class Statements and find that the query statement of 5.5 is different from the old one.
> The statement of 5.5 likes this:
> findAllDestinationsStatement = "SELECT DISTINCT CONTAINER FROM " + getFullAckTableName();
> while 5.2 is the following:
> findAllDestinationsStatement = "SELECT DISTINCT CONTAINER FROM " + getFullMessageTableName();
> In my option,JDBCAdapter should fetch all destinations from the message table,not ack table.
> Is it a mistake or what's the reason about this changing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira