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
Current behavior:
Basically if there is one valid active connection, and the same client tries to make another valid connection, server doesn't allow it throws error of duplicate clientid message. In scenarios when client is connected to server and in the middle it loses network there is no clear websocket disconnection and when the client wants to connects back the server isn't allowing, it ofcourse allows after some time.
Expected behavior:
In above stated scenario the new valid connection should go through.
Steps to reproduce:
Connect a client, disable wifi, connect back, it throws error of duplicate clientId.
Related code:
Note heartbeat is set to 10 mins
server.SetTimeoutConfig(ws.ServerTimeoutConfig{
PingWait: 900 * time.Second,
WriteWait: 10 * time.Second,
})
Other information:
insert the output here
@lorenzodonini Please suggest, we see server initiated pings is in future releases, is there workaround for now
The text was updated successfully, but these errors were encountered:
Mayuri-Mense
changed the title
Keep next connection charger's active and close previous connection
Server is not allowing to having next valid connection attempt, Throws duplicate clientId message
Dec 11, 2024
OCPP version:
[x] 1.6
[ ] 2.0.1
I'm submitting a ...
[x] bug report
[ ] feature request
Current behavior:
Basically if there is one valid active connection, and the same client tries to make another valid connection, server doesn't allow it throws error of duplicate clientid message. In scenarios when client is connected to server and in the middle it loses network there is no clear websocket disconnection and when the client wants to connects back the server isn't allowing, it ofcourse allows after some time.
Expected behavior:
In above stated scenario the new valid connection should go through.
Steps to reproduce:
Connect a client, disable wifi, connect back, it throws error of duplicate clientId.
Related code:
Other information:
@lorenzodonini Please suggest, we see server initiated pings is in future releases, is there workaround for now
The text was updated successfully, but these errors were encountered: