question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

problem with load balancer observe/write requests

See original GitHub issue

Hi,

Our project is trying to use cluster of leshan servers with load balancer. We are using dtls and secure connections. Without balancer everything working fine, but with load balancer we have a lot of

2020-09-01 15:09:07.680 DEBUG 8656 --- [/0.0.0.0:5684#5] o.e.c.scandium.dtls.Connection           : Handshake with [/172.19.1.157:56732] has failed
2020-09-01 15:09:07.680 DEBUG 8656 --- [/0.0.0.0:5684#5] o.e.californium.scandium.DTLSConnector   : Handshake with [/172.19.1.157:56732] failed, report error to deferred 1 messages
2020-09-01 15:09:07.680  WARN 8656 --- [/0.0.0.0:5684#5] s.a.l.c.MessageSenderErrorCallback       : onError of message send callback

org.eclipse.leshan.core.request.exception.SendFailedException: Unable to send request coap://172.19.1.157:56732/3/0/15
        at org.eclipse.leshan.core.californium.CoapAsyncRequestObserver.onSendError(CoapAsyncRequestObserver.java:167) [leshan-core-cf-1.1.0.jar!/:na]
        at org.eclipse.californium.core.coap.Message.setSendError(Message.java:1063) [californium-core-2.3.0.jar!/:na]
        at org.eclipse.californium.core.coap.Request.setSendError(Request.java:1131) [californium-core-2.3.0.jar!/:na]
        at org.eclipse.californium.core.network.CoapEndpoint$SendingCallback.onError(CoapEndpoint.java:1456) [californium-core-2.3.0.jar!/:na]
        at org.eclipse.californium.elements.RawData.onError(RawData.java:303) [element-connector-2.3.0.jar!/:na]
        at org.eclipse.californium.scandium.DTLSConnector$2.handshakeFailed(DTLSConnector.java:451) [scandium-2.3.0.jar!/:na]
        at org.eclipse.californium.scandium.dtls.Handshaker.handshakeFailed(Handshaker.java:1425) [scandium-2.3.0.jar!/:na]
        at org.eclipse.californium.scandium.DTLSConnector.processAlertRecord(DTLSConnector.java:1595) [scandium-2.3.0.jar!/:na]
        at org.eclipse.californium.scandium.DTLSConnector.processRecord(DTLSConnector.java:1330) [scandium-2.3.0.jar!/:na]
        at org.eclipse.californium.scandium.DTLSConnector$12.run(DTLSConnector.java:1195) [scandium-2.3.0.jar!/:na]
        at org.eclipse.californium.elements.util.SerialExecutor$1.run(SerialExecutor.java:276) [element-connector-2.3.0.jar!/:na]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_252]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_252]
        at java.lang.Thread.run(Thread.java:748) [na:1.8.0_252]
Caused by: org.eclipse.californium.scandium.dtls.HandshakeException: Received 'fatal alert'
        at org.eclipse.californium.scandium.DTLSConnector.processAlertRecord(DTLSConnector.java:1580) [scandium-2.3.0.jar!/:na]
        ... 6 common frames omitted

I’ve tried sending sync/async requests - seems it doesn’t change anything. Leshan version 1.1.0. Could you please help with possible solutions?

please let me know if more details needed.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
sbernard31commented, Sep 7, 2020

I’m not sure to really get your question, but the answer should be in : https://github.com/eclipse/leshan/wiki/Using-Leshan-server-in-a-cluster#shared-stores

If not, please try to reformulate your question.

0reactions
UnforgivenDcommented, Sep 7, 2020

You mean ResponseCallback from LeshanServer.send ? yes, this callback, thanks for explanation.

other a little bit not related question - if I’m using RedisRegistrationStore in servers, and one is failed, device connected to this server still will be able to communicate with new server, chosen by load balancer?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshoot your Application Load Balancers
You configured an AWS WAF web access control list (web ACL) to monitor requests to your Application Load Balancer and it blocked a...
Read more >
Troubleshoot External HTTP(S) Load Balancing - Google Cloud
The load balancer generates an HTTP 5XX response code when the connection to the backend has unexpectedly closed while sending the HTTP request...
Read more >
How do I troubleshoot and fix failing health checks ... - YouTube
How do I troubleshoot and fix failing health checks for Application Load Balancers ?
Read more >
Load Balancing Algorithms, Types and Techniques - Kemp
The method used to distribute incoming client requests to a server farm located behind LoadMaster is often called the load balancing “algorithm” and...
Read more >
What Is Load Balancing? How Load Balancers Work - NGINX
Changing which server receives requests from that client in the middle of the shopping session can cause performance issues or outright transaction failure....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found