[AMQ-3445] jdbcPersistenceAdapter will lose existing queues after a broker restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.2, 5.5.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Rasitha Wijesinghe
• Created: 10/Aug/11 16:23
• Updated: 02/May/13 02:29
• Resolved: 08/Feb/12 15:29

Description

When using jdbcPersistenceAdapter, if you restart the broker queues do not show up until they are manually created or a consumer re-connects. This is especially a problem for Virtual Topic consumers - for Virtual Topic consumers once the queue is created (and thereby subscribing to the virtual topic), they should get all messages published to the topic until consumer explicitly remove subscription by deleting the queue. With KahaDB this works correctly but not with jdbcPersistenceAdapter. Tried both 5.4.2 and 5.5 and both have the same issue.

To reproduce:
1. Setup broker using jdbcPersistenceAdapter
2. Go to web console and create a queue: Consumer.MyApp.VirtualTopic.FOO
3. Go to topics page and create a topic: VirtualTopic.FOO
4. Send a message with Persistent Delivery to the topic
5. Verify queue has the message
6. Restart the broker
7. BUG: queue does not show up
8. Go to topics page and repeat steps 3 & 4
9. repeat step 2
10. BUG: only the first message shows up in the queue.

Do the same test on KahaDB and queue shows up in step 7 (and because of that) you get both messages in step 10.

Issue Links

• depends upon: AMQ-3695 Failover using a JDBC Message Store and Virtual Topic can result in a lost message if queue is empty