You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing the Leshan client demo with a LwM2M Bootstrap server. The LwM2M Bootstrap server sends the Bootstrap write differently to the leshan Bootstrap server. Instead of the Uri-Path being /0/0 it sends it as /0 and puts the instance information in the TLV instead. I checked the OMA specifications 5.2.7.4 and this appears to be a valid case. This bootstrap write works on the wakaama client.
Here's a comparison:
LwM2M Server
Leshan Server
This is the error I'm getting from the leshan client demo
ERROR ObjectResource - Exception while handling request(CON-PUT MID=57584, Token=4410C188A2C5321A, OptionSet={"Uri-Path":"0", "Content-Format":"application/vnd.oma.lwm2m+tlv"},
<Removed packets> ) on the /0 resource
java.lang.NullPointerException
at org.eclipse.leshan.client.resource.ObjectEnabler.doWrite(ObjectEnabler.java:222)
at org.eclipse.leshan.client.resource.BaseObjectEnabler.write(BaseObjectEnabler.java:211)
at org.eclipse.leshan.client.californium.impl.ObjectResource.handlePUT(ObjectResource.java:231)
at org.eclipse.californium.core.CoapResource.handleRequest(CoapResource.java:223)
at org.eclipse.leshan.client.californium.impl.ObjectResource.handleRequest(ObjectResource.java:100)
at org.eclipse.californium.core.server.ServerMessageDeliverer.deliverRequest(ServerMessageDeliverer.java:108)
at org.eclipse.californium.core.network.stack.BaseCoapStack$StackTopAdapter.receiveRequest(BaseCoapStack.java:193)
at org.eclipse.californium.core.network.stack.AbstractLayer.receiveRequest(AbstractLayer.java:81)
at org.eclipse.californium.core.network.stack.AbstractLayer.receiveRequest(AbstractLayer.java:81)
at org.eclipse.californium.core.network.stack.BlockwiseLayer.receiveRequest(BlockwiseLayer.java:391)
at org.eclipse.californium.core.network.stack.ReliabilityLayer.receiveRequest(ReliabilityLayer.java:262)
at org.eclipse.californium.core.network.stack.AbstractLayer.receiveRequest(AbstractLayer.java:81)
at org.eclipse.californium.core.network.stack.BaseCoapStack.receiveRequest(BaseCoapStack.java:133)
at org.eclipse.californium.core.network.CoapEndpoint$1.receiveRequest(CoapEndpoint.java:240)
at org.eclipse.californium.core.network.UdpMatcher$2.run(UdpMatcher.java:251)
at org.eclipse.californium.elements.util.SerialExecutor$1.run(SerialExecutor.java:277)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
The text was updated successfully, but these errors were encountered:
I've been testing the Leshan client demo with a LwM2M Bootstrap server. The LwM2M Bootstrap server sends the Bootstrap write differently to the leshan Bootstrap server. Instead of the Uri-Path being /0/0 it sends it as /0 and puts the instance information in the TLV instead. I checked the OMA specifications 5.2.7.4 and this appears to be a valid case. This bootstrap write works on the wakaama client.
Here's a comparison:
LwM2M Server
Leshan Server
This is the error I'm getting from the leshan client demo
The text was updated successfully, but these errors were encountered: