[
https://issues.apache.org/jira/browse/APLO-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved APLO-310.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.7
Assignee: Hiram Chirino
The problem is actually more fundamental. Wildcard durable subs would not
match topics created after the durable sub was setup.
When starting up, in one case the topic would have been created already, in the
other they did not exist yet.
This should be fixed up in the next snapshot.
> Dsubs are not always created from apollo.xml
> --------------------------------------------
>
> Key: APLO-310
> URL: https://issues.apache.org/jira/browse/APLO-310
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20130221.165856-207
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.7
>
>
> I'm trying to define a dsub with wildcard subscription in apollo.xml and it
> seems that the topic consumers are not always created.
> Here is what I have in apollo.xml:
> <topic id="foo.1"/>
> <topic id="foo.2"/>
> <dsub id="bar" topic="foo.*"/>
> If I stop Apollo, destroy its data directory and start it again, the
> consumers are created. Via the REST API I see on each topic:
> {
> 'config' => {
> 'id' => 'foo.1',
> 'other' => []
> },
> 'dsubs' => [
> 'bar'
> ],
> 'id' => 'foo.1',
> 'metrics' => {
> 'consumer_count' => 1,
> [...]
> }
> So far so good.
> If I restart Apollo (service apollo restart), the dsub consumer does not
> appear anymore:
> {
> 'config' => {
> 'id' => 'foo.1',
> 'other' => []
> },
> 'dsubs' => [],
> 'id' => 'foo.1',
> 'metrics' => {
> 'consumer_count' => 0,
> [...]
> }
> This looks like a conflict between apollo.xml and what the store knows about
> dsubs...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
