Hello, We are having and Issue when sending request on elektron websocket cloud Api:
"{Type": "Status", "State": { "Stream": "Closed", "Data": "Suspect", "Text": "Request Rejected: Channel not logged in.", "Code": "AlreadyOpen" }, "ID": 2, "Key": {"Service": "ELEKTRON_DD"} }]
I've read that ExceededMaxMountsPerUser occurred when multiple instance try to log in with the same credentials...Is there a way to kill all other connections at the authentification process ? takeExclusiveSignOnControl does not seems to work
Hi @adime,
The takeExclusiveSignOnControl should work. The expected behavior is that if instance1 is running and you attempt to establish a new connection with instance2, both applications will be connected for a short window of time until instance1 tries to refresh it’s access token it will be kicked out.
In your case, is it instance2 that fails immediately?
Thank you for your answer !
Yes it's the instance 2 that fails immediately but it's seems to work when i retry by changing my cloud hostname from amer-1.pricing.. to amer-2.pricing...
I don't known why the first host is still rejecting our server.
Hi @adime,
When instance2 does succeed, does instance1 eventually fail to establish a new access token?