You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by akos <ak...@p92.hu> on 2010/03/23 12:14:43 UTC
Durable subscription discrepancies.
Hi All,
i'm trying to use durable subscriptions and i found so many
bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
- if i set keepDurableSubsActive=false (what i want) then i won't get the
messages after re(!)-activation. I've figured out that the
DurableTopicSubscription.deactivate() invokes
StoreDurableSubscriberCursor.remove() what is removes the TopicStorePrefetch
from the topic. Up to this point everyting is fine. But when the durable
subscription becomes active the StoreDurableSubscriberCursor.add won't be
called. So DurableTopicSubscription.activate() does not put the cursor back.
- if i keep the keepDurableSubsActive=true setting (i don't want to) then
the Topic.activate() re(!)-adds the subscription to the consumers list.
Every re-activation increases the list.
- there is another problem in the jmx broker also. The
ManagedRegionBroker.addInactiveSubscription adds the subscription to this
domain: "...Type=Subscription,active=false,name=...". I don't know what this
active=false part supposed to mean, but it puts the MBean to a strange path
in the jconsole. What is not a big problem, but it is not managed by the
rest of the code. Even if a subscription is inactivated the MBean in the
"Durable" section shows active. If the subscription is active the "false"
section contains an entry as it would be inactive.
Could you please tell me some hints, how can i fix (mostly) the first one?
Thanks for helping!
akos
--
View this message in context: http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Durable subscription discrepancies.
Posted by akos <ak...@p92.hu>.
Last case: https://issues.apache.org/activemq/browse/AMQ-2666
Gary Tully wrote:
>
> Have a look at this test case, it should be provide you with examples and
> with a good starting point:
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
>
> On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
>
>> Can you open a jira issue and submit a junit test case, this will help
>> fully understand your scenario.
>>
>>
>> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>>
>>>
>>> Hi All,
>>>
>>> i'm trying to use durable subscriptions and i found so many
>>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>>>
>>> - if i set keepDurableSubsActive=false (what i want) then i won't get
>>> the
>>> messages after re(!)-activation. I've figured out that the
>>> DurableTopicSubscription.deactivate() invokes
>>> StoreDurableSubscriberCursor.remove() what is removes the
>>> TopicStorePrefetch
>>> from the topic. Up to this point everyting is fine. But when the durable
>>> subscription becomes active the StoreDurableSubscriberCursor.add won't
>>> be
>>> called. So DurableTopicSubscription.activate() does not put the cursor
>>> back.
>>>
>>> - if i keep the keepDurableSubsActive=true setting (i don't want to)
>>> then
>>> the Topic.activate() re(!)-adds the subscription to the consumers list.
>>> Every re-activation increases the list.
>>>
>>> - there is another problem in the jmx broker also. The
>>> ManagedRegionBroker.addInactiveSubscription adds the subscription to
>>> this
>>> domain: "...Type=Subscription,active=false,name=...". I don't know what
>>> this
>>> active=false part supposed to mean, but it puts the MBean to a strange
>>> path
>>> in the jconsole. What is not a big problem, but it is not managed by the
>>> rest of the code. Even if a subscription is inactivated the MBean in the
>>> "Durable" section shows active. If the subscription is active the
>>> "false"
>>> section contains an entry as it would be inactive.
>>>
>>> Could you please tell me some hints, how can i fix (mostly) the first
>>> one?
>>>
>>> Thanks for helping!
>>> akos
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> http://blog.garytully.com
>>
>> Open Source Integration
>> http://fusesource.com
>>
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
>
--
View this message in context: http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p28015242.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Durable subscription discrepancies.
Posted by akos <ak...@p92.hu>.
Jira for the second one: https://issues.apache.org/activemq/browse/AMQ-2665
Gary Tully wrote:
>
> Have a look at this test case, it should be provide you with examples and
> with a good starting point:
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
>
> On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
>
>> Can you open a jira issue and submit a junit test case, this will help
>> fully understand your scenario.
>>
>>
>> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>>
>>>
>>> Hi All,
>>>
>>> i'm trying to use durable subscriptions and i found so many
>>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>>>
>>> - if i set keepDurableSubsActive=false (what i want) then i won't get
>>> the
>>> messages after re(!)-activation. I've figured out that the
>>> DurableTopicSubscription.deactivate() invokes
>>> StoreDurableSubscriberCursor.remove() what is removes the
>>> TopicStorePrefetch
>>> from the topic. Up to this point everyting is fine. But when the durable
>>> subscription becomes active the StoreDurableSubscriberCursor.add won't
>>> be
>>> called. So DurableTopicSubscription.activate() does not put the cursor
>>> back.
>>>
>>> - if i keep the keepDurableSubsActive=true setting (i don't want to)
>>> then
>>> the Topic.activate() re(!)-adds the subscription to the consumers list.
>>> Every re-activation increases the list.
>>>
>>> - there is another problem in the jmx broker also. The
>>> ManagedRegionBroker.addInactiveSubscription adds the subscription to
>>> this
>>> domain: "...Type=Subscription,active=false,name=...". I don't know what
>>> this
>>> active=false part supposed to mean, but it puts the MBean to a strange
>>> path
>>> in the jconsole. What is not a big problem, but it is not managed by the
>>> rest of the code. Even if a subscription is inactivated the MBean in the
>>> "Durable" section shows active. If the subscription is active the
>>> "false"
>>> section contains an entry as it would be inactive.
>>>
>>> Could you please tell me some hints, how can i fix (mostly) the first
>>> one?
>>>
>>> Thanks for helping!
>>> akos
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> http://blog.garytully.com
>>
>> Open Source Integration
>> http://fusesource.com
>>
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
>
--
View this message in context: http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p28014699.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Durable subscription discrepancies.
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi,
yes, osgi core is now a dependency.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Mar 24, 2010 at 10:50 AM, akos <ak...@p92.hu> wrote:
>
> By the way, I need 'org.osgi.core-4.1.0.jar' from the 5.3.1 optional libs
> to
> be able to start my broker, what was not needed in 5.3. Is it ok?
>
>
> Gary Tully wrote:
> >
> > Have a look at this test case, it should be provide you with examples and
> > with a good starting point:
> >
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
> >
> > On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
> >
> >> Can you open a jira issue and submit a junit test case, this will help
> >> fully understand your scenario.
> >>
> >>
> >> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
> >>
> >>>
> >>> Hi All,
> >>>
> >>> i'm trying to use durable subscriptions and i found so many
> >>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
> >>>
> >>> - if i set keepDurableSubsActive=false (what i want) then i won't get
> >>> the
> >>> messages after re(!)-activation. I've figured out that the
> >>> DurableTopicSubscription.deactivate() invokes
> >>> StoreDurableSubscriberCursor.remove() what is removes the
> >>> TopicStorePrefetch
> >>> from the topic. Up to this point everyting is fine. But when the
> durable
> >>> subscription becomes active the StoreDurableSubscriberCursor.add won't
> >>> be
> >>> called. So DurableTopicSubscription.activate() does not put the cursor
> >>> back.
> >>>
> >>> - if i keep the keepDurableSubsActive=true setting (i don't want to)
> >>> then
> >>> the Topic.activate() re(!)-adds the subscription to the consumers list.
> >>> Every re-activation increases the list.
> >>>
> >>> - there is another problem in the jmx broker also. The
> >>> ManagedRegionBroker.addInactiveSubscription adds the subscription to
> >>> this
> >>> domain: "...Type=Subscription,active=false,name=...". I don't know what
> >>> this
> >>> active=false part supposed to mean, but it puts the MBean to a strange
> >>> path
> >>> in the jconsole. What is not a big problem, but it is not managed by
> the
> >>> rest of the code. Even if a subscription is inactivated the MBean in
> the
> >>> "Durable" section shows active. If the subscription is active the
> >>> "false"
> >>> section contains an entry as it would be inactive.
> >>>
> >>> Could you please tell me some hints, how can i fix (mostly) the first
> >>> one?
> >>>
> >>> Thanks for helping!
> >>> akos
> >>>
> >>> --
> >>> View this message in context:
> >>>
> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
> >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>>
> >>>
> >>
> >>
> >> --
> >> http://blog.garytully.com
> >>
> >> Open Source Integration
> >> http://fusesource.com
> >>
> >
> >
> >
> > --
> > http://blog.garytully.com
> >
> > Open Source Integration
> > http://fusesource.com
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p28012750.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: Durable subscription discrepancies.
Posted by akos <ak...@p92.hu>.
By the way, I need 'org.osgi.core-4.1.0.jar' from the 5.3.1 optional libs to
be able to start my broker, what was not needed in 5.3. Is it ok?
Gary Tully wrote:
>
> Have a look at this test case, it should be provide you with examples and
> with a good starting point:
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
>
> On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
>
>> Can you open a jira issue and submit a junit test case, this will help
>> fully understand your scenario.
>>
>>
>> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>>
>>>
>>> Hi All,
>>>
>>> i'm trying to use durable subscriptions and i found so many
>>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>>>
>>> - if i set keepDurableSubsActive=false (what i want) then i won't get
>>> the
>>> messages after re(!)-activation. I've figured out that the
>>> DurableTopicSubscription.deactivate() invokes
>>> StoreDurableSubscriberCursor.remove() what is removes the
>>> TopicStorePrefetch
>>> from the topic. Up to this point everyting is fine. But when the durable
>>> subscription becomes active the StoreDurableSubscriberCursor.add won't
>>> be
>>> called. So DurableTopicSubscription.activate() does not put the cursor
>>> back.
>>>
>>> - if i keep the keepDurableSubsActive=true setting (i don't want to)
>>> then
>>> the Topic.activate() re(!)-adds the subscription to the consumers list.
>>> Every re-activation increases the list.
>>>
>>> - there is another problem in the jmx broker also. The
>>> ManagedRegionBroker.addInactiveSubscription adds the subscription to
>>> this
>>> domain: "...Type=Subscription,active=false,name=...". I don't know what
>>> this
>>> active=false part supposed to mean, but it puts the MBean to a strange
>>> path
>>> in the jconsole. What is not a big problem, but it is not managed by the
>>> rest of the code. Even if a subscription is inactivated the MBean in the
>>> "Durable" section shows active. If the subscription is active the
>>> "false"
>>> section contains an entry as it would be inactive.
>>>
>>> Could you please tell me some hints, how can i fix (mostly) the first
>>> one?
>>>
>>> Thanks for helping!
>>> akos
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> http://blog.garytully.com
>>
>> Open Source Integration
>> http://fusesource.com
>>
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
>
--
View this message in context: http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p28012750.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Durable subscription discrepancies.
Posted by akos <ak...@p92.hu>.
Thank you very much!
Here is a jira/junit for the first case:
https://issues.apache.org/activemq/browse/AMQ-2663
Gary Tully wrote:
>
> Have a look at this test case, it should be provide you with examples and
> with a good starting point:
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
>
> On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
>
>> Can you open a jira issue and submit a junit test case, this will help
>> fully understand your scenario.
>>
>>
>> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>>
>>>
>>> Hi All,
>>>
>>> i'm trying to use durable subscriptions and i found so many
>>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>>>
>>> - if i set keepDurableSubsActive=false (what i want) then i won't get
>>> the
>>> messages after re(!)-activation. I've figured out that the
>>> DurableTopicSubscription.deactivate() invokes
>>> StoreDurableSubscriberCursor.remove() what is removes the
>>> TopicStorePrefetch
>>> from the topic. Up to this point everyting is fine. But when the durable
>>> subscription becomes active the StoreDurableSubscriberCursor.add won't
>>> be
>>> called. So DurableTopicSubscription.activate() does not put the cursor
>>> back.
>>>
>>> - if i keep the keepDurableSubsActive=true setting (i don't want to)
>>> then
>>> the Topic.activate() re(!)-adds the subscription to the consumers list.
>>> Every re-activation increases the list.
>>>
>>> - there is another problem in the jmx broker also. The
>>> ManagedRegionBroker.addInactiveSubscription adds the subscription to
>>> this
>>> domain: "...Type=Subscription,active=false,name=...". I don't know what
>>> this
>>> active=false part supposed to mean, but it puts the MBean to a strange
>>> path
>>> in the jconsole. What is not a big problem, but it is not managed by the
>>> rest of the code. Even if a subscription is inactivated the MBean in the
>>> "Durable" section shows active. If the subscription is active the
>>> "false"
>>> section contains an entry as it would be inactive.
>>>
>>> Could you please tell me some hints, how can i fix (mostly) the first
>>> one?
>>>
>>> Thanks for helping!
>>> akos
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> http://blog.garytully.com
>>
>> Open Source Integration
>> http://fusesource.com
>>
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
>
--
View this message in context: http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p28012619.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Durable subscription discrepancies.
Posted by Gary Tully <ga...@gmail.com>.
Have a look at this test case, it should be provide you with examples and
with a good starting point:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubscriptionTestSupport.java?view=markup
On 23 March 2010 16:14, Gary Tully <ga...@gmail.com> wrote:
> Can you open a jira issue and submit a junit test case, this will help
> fully understand your scenario.
>
>
> On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>
>>
>> Hi All,
>>
>> i'm trying to use durable subscriptions and i found so many
>> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>>
>> - if i set keepDurableSubsActive=false (what i want) then i won't get the
>> messages after re(!)-activation. I've figured out that the
>> DurableTopicSubscription.deactivate() invokes
>> StoreDurableSubscriberCursor.remove() what is removes the
>> TopicStorePrefetch
>> from the topic. Up to this point everyting is fine. But when the durable
>> subscription becomes active the StoreDurableSubscriberCursor.add won't be
>> called. So DurableTopicSubscription.activate() does not put the cursor
>> back.
>>
>> - if i keep the keepDurableSubsActive=true setting (i don't want to) then
>> the Topic.activate() re(!)-adds the subscription to the consumers list.
>> Every re-activation increases the list.
>>
>> - there is another problem in the jmx broker also. The
>> ManagedRegionBroker.addInactiveSubscription adds the subscription to this
>> domain: "...Type=Subscription,active=false,name=...". I don't know what
>> this
>> active=false part supposed to mean, but it puts the MBean to a strange
>> path
>> in the jconsole. What is not a big problem, but it is not managed by the
>> rest of the code. Even if a subscription is inactivated the MBean in the
>> "Durable" section shows active. If the subscription is active the "false"
>> section contains an entry as it would be inactive.
>>
>> Could you please tell me some hints, how can i fix (mostly) the first one?
>>
>> Thanks for helping!
>> akos
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
Re: Durable subscription discrepancies.
Posted by Gary Tully <ga...@gmail.com>.
Can you open a jira issue and submit a junit test case, this will help fully
understand your scenario.
On 23 March 2010 11:14, akos <ak...@p92.hu> wrote:
>
> Hi All,
>
> i'm trying to use durable subscriptions and i found so many
> bugs/discrepancies in that area (AMQ 5.3). It is really frustrating.
>
> - if i set keepDurableSubsActive=false (what i want) then i won't get the
> messages after re(!)-activation. I've figured out that the
> DurableTopicSubscription.deactivate() invokes
> StoreDurableSubscriberCursor.remove() what is removes the
> TopicStorePrefetch
> from the topic. Up to this point everyting is fine. But when the durable
> subscription becomes active the StoreDurableSubscriberCursor.add won't be
> called. So DurableTopicSubscription.activate() does not put the cursor
> back.
>
> - if i keep the keepDurableSubsActive=true setting (i don't want to) then
> the Topic.activate() re(!)-adds the subscription to the consumers list.
> Every re-activation increases the list.
>
> - there is another problem in the jmx broker also. The
> ManagedRegionBroker.addInactiveSubscription adds the subscription to this
> domain: "...Type=Subscription,active=false,name=...". I don't know what
> this
> active=false part supposed to mean, but it puts the MBean to a strange path
> in the jconsole. What is not a big problem, but it is not managed by the
> rest of the code. Even if a subscription is inactivated the MBean in the
> "Durable" section shows active. If the subscription is active the "false"
> section contains an entry as it would be inactive.
>
> Could you please tell me some hints, how can i fix (mostly) the first one?
>
> Thanks for helping!
> akos
>
> --
> View this message in context:
> http://old.nabble.com/Durable-subscription-discrepancies.-tp27999389p27999389.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com