[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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Message Store
• Labels: jdbcstorage
• Assignee: Unassigned
• Reporter: SuoNayi
• Created: 06/Jan/12 16:19
• Updated: 13/Feb/12 08:48
• Resolved: 07/Jan/12 19:24

Description

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?

Issue Links

• duplicates: AMQ-3526 JDBC persistence adapter, destination mbeans not visible on restart till producers or consumers reattach
• is duplicated by: AMQ-3712 ActiveMQ browser shows negative message count with messages dequeued count greater than messages enqueued