Done https://github.com/eclipse/leshan/issues/243
I see. Would you care to open in issue for this so that it doesn't get lost?
I think this might just be a question of synchronizing on the socket...
--
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht Charlottenburg,
HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
On Thu, 2016-12-22 at 13:28 +0000, Michael Huelfenhaus wrote:
We use the standard lwm2m port for secure connections.
Am 22.12.2016 um 12:16 schrieb Kai <sophokles.kh@xxxxxxxxx>:
I assume, however, that these bind to different ports, right?
On Thu, Dec 22, 2016 at 11:19 AM Michael Huelfenhaus <m.huelfenhaus@davengo.c
om> wrote:
This happens on the server, we have 2 LWM Server running in Docker
containers on different machines.
Am 14.12.2016 um 18:49 schrieb Kai <sophokles.kh@xxxxxxxxx>:
Does this happen on the client or the server side? It might be due to
multiple threads trying to send a datagram over the socket concurrently.
I am not sure if we explicitly synchronize access to the socket...
Kai
Michael Huelfenhaus <m.huelfenhaus@xxxxxxxxxxx> schrieb am Mi., 14. Dez.
2016, 13:26:
Hi,
i am getting Could not send datagram error with multiple LWM Servers
with M14, any ideas?
Could not send datagram java.io.IOException: Operation not permitted at
java.net.PlainDatagramSocketImpl.send(Native Method) at
java.net.DatagramSocket.send(DatagramSocket.java:693) at
org.eclipse.californium.scandium.DTLSConnector.sendDatagram(DTLSConnect
or.java:1341)
at
org.eclipse.californium.scandium.DTLSConnector.sendFlight(DTLSConnector
.java:1322) at
org.eclipse.californium.scandium.DTLSConnector.handleTimeout(DTLSConnec
tor.java:1360) at
org.eclipse.californium.scandium.DTLSConnector.access$600(DTLSConnector
.java:112)
at
org.eclipse.californium.scandium.DTLSConnector$RetransmitTask.run(DTLSC
onnector.java:1494) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ac
cess$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ru
n(ScheduledThreadPoolExecutor.java:293) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja
va:1142) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j
ava:617)
at java.lang.Thread.run(Thread.java:745)
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
|
