Andrea Selva

I don't know when I'll have free time to dedicate to this, sorry On Mon, Apr 8, 2019 at 5:45 PM giri110890 wrote: > Hi @andsel Thanks for the quick...

@abonstu as I wrote in the comment of 8th April the solution could be to provide an API as a `close(clientId)` method at broker level. If you want you could...

`sessions.disconnect(cliID)` should does a clean disconnect, while the other drop the socket channel

Hi @mstranne which version of moquette are you using? since version 0.10 moquette in in the namespace io.moquette and not org.eclipse.moquette. Only the latest version of moquette is supported.

I don't have too much experience with Android, giving a look at stacktrace seems like that Android didn't find something, but probably the stack trace is more wide than you...

Hi @necoicould thank's for reporting it, in order to investigate it: - could you describe better how to create a reproducer? - could you reproduce it outside of Android environment?...

Thanks @kazetsukaimiko to throw the ball for discussion. Those interfaces was created because Moquette initially used `MapDB` as local KV storage, then switched to `H2 MVStore` because H2 is more...

> Its possible you could externalize some of your concerns around providing an SPI by piggybacking on existing known interfaces, something like the JSR-107 API or just java.lang.Map in this...

Hi @zexin321 I saw your PR #633 I would like to have some profiling tests that we can share to have a common base to discuss on. Please could add...

I have to reason about this more carefully, because this could potentially open to memory leakeage