Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server is not allowing to having next valid connection attempt, Throws duplicate clientId message #314

Open
Mayuri-Mense opened this issue Dec 11, 2024 · 0 comments

Comments

@Mayuri-Mense
Copy link

Mayuri-Mense commented 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:

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

@Mayuri-Mense 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant