Archived

This forum has been archived. Please start a new discussion on GitHub.

[BerkeleyDB] Memory allocation exception when start the service

dakotadelnorte
dakotadelnorte
in Help Center
Hi,

We have a problem with our service when it is restarted because it try to use the db (used by IceStorm) in memory and cannot load because is very big (memory allocation exception).

We configured the needed property in order to load a lot of objects, but this solution work and it is good but is not a full solution. Then, exists any way to expire the element subscribed to a Topic automatically by the framework? Or we need unsubscribe mnually when we need?

Thank you in advance.

Best regards,

Comments

  • bernard
    bernard Jupiter, FL
    Hi Roberto,

    You control when unreachable subscribers are removed by the IceStorm service: see https://doc.zeroc.com/display/Ice36/IceStorm+Quality+of+Service.

    This QoS applies only to subscribers to which IceStorm attempts to send a message. If a subscriber subscribes to a topic but no event is ever sent to this topic, IceStorm does not ever check this subscriber.

    A subscription is not that big, so you must have a very large number of subscribers (including stale subscribers) to run out of memory. I am wondering if it could be a different problem. Do you also create a large number of topics? Could you provide the actual exception and error message you're seeing?

    Best regards,
    Bernard

Categories