activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rasitha Wijesinghe (JIRA)" <>
Subject [jira] [Created] (AMQ-3445) jdbcPersistenceAdapter will lose existing queues after a broker restart
Date Wed, 10 Aug 2011 16:25:27 GMT
jdbcPersistenceAdapter will lose existing queues after a broker restart

                 Key: AMQ-3445
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.0, 5.4.2
            Reporter: Rasitha Wijesinghe

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.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message