java.lang.IllegalStateException when connecting about javacord

[Bastian]

Hey,

api.setWaitForServersOnStartup(false);

works as a temporary fix. I still have to find out the reason for this error, but this is at least a temporary solution for everyone with this problem (It seems to not affect everyone).

[Bastian]

Are there still people experiencing this bug?

[Bastian]

Hey,
Can you please enable the debug mode and see if there is any additional information?

[pcr3w]

There's no other information with debug mode on (I'm assuming that you mean the logger debug mode).

[pcr3w]

That seems to be working for the moment - thanks.

[iiiLollo]

I noticed the following, I get this error when I try to connect to a server after my connection didn't close property. This can happen if the application running the api crashes before running the api.disconnect() command.

But I also noticed that api.disconnect() sometimes doesn't close the connection properly,
I found the following lines in the log after running api.disconnect(), it looks like it's trying to connect again.

d.b.j.utils.DiscordWebsocketAdapter - Websocket closed with reason null and code 1000 by client!
d.b.j.utils.DiscordWebsocketAdapter - Sending resume packet
d.b.j.utils.DiscordWebsocketAdapter - Received HELLO packet
d.b.j.utils.DiscordWebsocketAdapter - Could not resume session. Reconnecting now...
d.b.j.utils.DiscordWebsocketAdapter - Sending identify packet

[Yorkforce]

@BtoBastian Has there been any update on this at all? We have always had this problem every couple of weeks or so, but we have always been able to use the discord reconnect command a few times to eventually get it to connect, however right now it will not connect at all, i just tried running the discord reconnect command over 50 times on one of our servers and it just won't have it.

[Bastian]

Hey,
if you have debugging enabled, what is the full log?
Is there a Received READY packet before receiving the error?
Is there a Websocket closed ... message?

[Yorkforce]

This is what the logs are showing:
[20:01:27] [ReadingThread/DEBUG] [de.btobastian.javacord.utils.DiscordWebsocketAdapter/sponge]: Received READY packet [20:01:29] [WritingThread/DEBUG] [de.btobastian.javacord.utils.DiscordWebsocketAdapter/sponge]: Websocket closed with reason No more WebSocket frame from the server. and code 1002 by client! Trying to resume connection.

This morning it seems better, I just checked and only 2 servers hadn't automatically reconnected (they auto restart every 8 hours) and running the discord reconnect commands on those 2 servers both reconnected straight away but the problem will eventually return again and there will be periods of time where we are unable to connect at all, as was the case last night.

[Bastian]

And afterwards the Socket closed before ready packet was received message?

[Yorkforce]

Yep directly afterwards:
https://pastebin.com/AT28YtQx

[AldeRoberge]

Hello Bastian, I've encountered this bug. I'll keep you updated if updating to the latest Javacord version fixes it!

Edit : Actually yes, updating to 2.0.17 did it for me