Subscription not expiring

[afuggini]

I'm subscribing through Iron Router's waitOn. I initiated an instance as:

App.Subs = new SubsManager(
  cacheLimit: 20
  expireIn: 1
)

Then did App.Subs.subscribe 'inventory' within waitOn but after I change the route and wait for 1 minute, documents are still there if I query them using the client console.

Any ideas? Thank you!

[joegoldbeck]

+1. Subscription still seems to be active in Meteor.default_connection._subscriptions too

[afuggini]

@arunoda What are we missing here?

[arunoda]

Can I have a sample case? may be a simple app?

[dnish]

+1 not working

@arunoda You can check it with a simple app that uses a subscription. The subscription data is still available after the expire time. I've tried it on a chat application, set expireIn to 1 minute and still got messages after 5 minutes.

[vuhrmeister]

+1

I experienced the same issue. I can give an example.

I have a list with a pagination:

---- Item 1 ----
---- Item 2 ----
---- Item 3 ----

< | 1 | 2 | 3 | >

Initially (being on page 1) I subscribe to the list collection with skip and limit param to get only results for the first page. Navigating to page 2 subscribes to the same publication but with different skip value.

Now let's count the documents (the result is as expected):

MyCollection.find().count() // => 6

Let's wait until the subscriptions are expired (after expireIn) and count again:

MyCollection.find().count() // => 6

So even when the subscriptions are expired all documents are still cached.

Going back to page 1 count() would still return 6.

Let's wait again until the subscription is expired. Now we navigate to page 3.
What happens?

MyCollection.find().count() // => 3

So only when subscribing with different parameters the old subscriptions are actually removed!

I hope that helps.

For the moment I need to increase expireIn to something high for not getting trouble when paging through the list.