Re: [milo-dev] [Q] Timing for deleting Subscription and MonitoredItems

[Kevin Herron <kevinherron@xxxxxxxxx>]

They should get deleted when the session either times out or is closed by the client.

If the client is disconnecting without closing the session, and the session timeout was significant, this could result in the number of orphaned sessions (and the associated subscriptions and items) growing.

I'll take a look and make sure that session are timing out and being cleaned up correctly as well, just in case.

On Tue, Jan 16, 2018 at 5:05 PM, Shigeru Ishida <ishida_shigeru@xxxxxxxxxxx> wrote:

Hi Kevin,

When will information of Subscription and MonitoredItems created by
the server be deleted ?

Will the server automatically delete these information when default
mechanism of Milo works when the client terminates the connection
normally or when the client terminates unexpectedly ?
(ex. kill -9 client-pid)

Or is it necessary for the client to record the SubscriptionId previously
used and throw a delete request to the server when the client is restarted ?

Here, with Apache Felix removed, the server is running stably.
Once the re-establishing process has been executed, createSubscription()
and createMonitoredItems() are called and processing continues.

Therefore, a simulation server assuming process lines, process units,
and node items of a factory with a larger scale is also created and running
continuously. The total number of node items of this simulation server is
over 10,000.

Another company's client product is connected to this server, and OOME has
occurred on the server as a result of this client repeatedly connecting and
disconnecting.

Regards,

--Shigeru
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/milo-dev