[cf-dev] Clean-up mechanism for blockwise transfer is removing observe s

[Gilles Cannenterre <gcannenterre@xxxxxxxxxxxxxxxxxx>]

Hi all,

I have been using observe on a big object requiring Block2 option on the initial observe request.
This is handled nicely on leshan sandbox server but after sometimes (a few minutes) the notification associated to the said object are rejected with CoAP reset messages.
I have switched back to a local leshan instance and noted that prior to the notification being rejected I have this message in the server console:

Dec 16, 2015 5:13:01 PM org.eclipse.californium.core.network.stack.BlockwiseLayer$BlockCleanupTask run
INFO: Block2 transfer timed out: CON-GET    MID= 2565, Token=e0d964cec5, OptionSet={"Observe":0, "Uri-Path":["<my object id here>","0"]}, no payload

It seems like the blockwise transfer cleaning task is cleaning to much... 


Gilles