I had a similar report earlier for data above 100 MiB, yet this probably depends just on the block size. I opened a bug
in Eclipse’s Bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=471101
Could you please add a stacktrace as a comment?
I will try to eventually find some time next week to go ahead with debugging and fixing.
Thanks for the report
Matthias
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mrinal Sharma
Sent: Freitag, 26. Juni 2015 04:44
To: cf-dev@xxxxxxxxxxx
Subject: [cf-dev] CoAP error while writing large LWM2M Object
I am using Leshan LWM2M server for client server communication. It internally uses Californium CoAP server. I am seeing an error while writing a String resource with 1 MB of data.
During the send operation of resource from Server to Client, I see a given below error error. This is 100% reproducible.
ACK-5.00 MID=15578, Token=9233882e, OptionSet={"Block1":12358}, ""
This response is handled in method BlockwiseLayer::receiveResponse()
Below is the code snippet of method where the response is handled.
else if (!response.getOptions().hasBlock2()) {
// All request block have been acknowledged and we receive a piggy-backed
// response that needs no blockwise transfer. Thus, deliver it.
super.receiveResponse(exchange, response);
} else {
Can someone help me to resolve this issue?