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

XMage disconnects from server every 30 secs #5444

Open
JayDi85 opened this Issue Nov 26, 2018 · 13 comments

Comments

Projects
None yet
4 participants
@JayDi85
Copy link
Member

JayDi85 commented Nov 26, 2018

@LevelX2 There are disconnection issues on xmage.de after update to 32v0 -- every 30 secs players and watchers disconnected from server by error (only if they join/watch game). I can't reproduce that problem with local server. It's can be xmage.de issue only.

INFO  2018-11-27 00:00:53,476 Watching game 2336b16a-d606-4956-9069-0ddd3158eebb                                         =>[AWT-EventQueue-0] CallbackClientImpl.watchGame 
INFO  2018-11-27 00:01:15,749 connection to server lost - Could not connect to server!                                   =>[Thread-10585] SessionImpl$ClientConnectionListener.handleConnectionException 
java.lang.Exception: Could not connect to server!
	at org.jboss.remoting.Client.notifyListeners(Client.java:1886)
	at org.jboss.remoting.LeasePinger.stopPing(LeasePinger.java:134)
	at org.jboss.remoting.MicroRemoteClientInvoker.terminateLease(MicroRemoteClientInvoker.java:434)
	at org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask.run(ConnectionValidator.java:1108)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
INFO  2018-11-27 00:01:15,750 RECONNECT - Connected: true                                                                =>[Thread-10585] SessionImpl.reconnect 
INFO  2018-11-27 00:01:15,750 DISCONNECTED (NO Event Dispatch Thread)                                                    =>[Thread-10585] MageFrame.disconnected 
INFO  2018-11-27 00:01:16,229 DISCONNECT (still connected)                                                               =>[AWT-EventQueue-0] SessionImpl.disconnect 
INFO  2018-11-27 00:01:16,307 Disconnected ...                                                                           =>[AWT-EventQueue-0] SessionImpl.disconnect 
INFO  2018-11-27 00:01:16,307 DISCONNECTED (Event Dispatch Thread)   
@LordNex

This comment has been minimized.

Copy link

LordNex commented Nov 26, 2018

Was the update rolled back? I got home and went to update the server, got everything updated and my customization and user db moved back over, but when I update my local home workstation and connect (Client or Admin) its still saying version 1.4.31V4.

I double checked and even made sure to download the update through the launcher and then move the folder where I have it secured. But it still comes up V1.4.31V4. Although in the launcher it says I have version 1.4.32V1OLD.

Im also still seeing vapormage.com as the primary USA server.

Reading config from http://xmage.de/xmage/config.json
Java version installed: 1.8.0_191
Java version available: 1.8.0_191
XMage version installed: 1.4.32V1OLD (2018-11-26)
XMage version available: 1.4.32V1OLD (2018-11-26)

As far as disconnects, I havenet seen anything like that yet on powersofwar.com

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Nov 26, 2018

Yes, I think it was rollbacked.

@LordNex

This comment has been minimized.

Copy link

LordNex commented Nov 26, 2018

Cool, thanks

Let me know if there's anything I can do to help

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Nov 26, 2018

It's not me... LevelX2 is server's admin and releaser. You was able to update your server to new version and checks disconnects. But it's late after rollback. Waiting info from LevelX2.

@LordNex

This comment has been minimized.

Copy link

LordNex commented Nov 26, 2018

No i don't think i ever got the newer version. I think by time I got home the rollback had already happened. It wasn't until I started looking at the version numbers and then checking here that I seen there was a issue. Thanks man, I'll keep an eye out for it to re-release

@LevelX2

This comment has been minimized.

Copy link
Contributor

LevelX2 commented Nov 26, 2018

Yes i used the name "1.4.32V1OLD" to get the launcher updater to rollback to 1.4.31V4.

I have not found a hint what's causing the disconnects every 30 seconds.
There is nothing specific reported in the server log.
Also my client was disconnect often only after connection to the server and not even joining/watching a game.

@LevelX2

This comment has been minimized.

Copy link
Contributor

LevelX2 commented Nov 27, 2018

Anyone any idea which commit/change yould have influence on network stability and so causing the disconnects?

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Nov 27, 2018

There were some threads dependency code for AI rating in drafts (read data from resources) -- but it have synchronized code and only for drafts: 6f93abf

Can you show server logs for disconnect errors?

@LevelX2

This comment has been minimized.

Copy link
Contributor

LevelX2 commented Nov 27, 2018

mageserver.log

That's the log.

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Nov 27, 2018

@LevelX2 there were same problems with old versions long ago (search).

Look at #586 -- it's have your recommend settings for public server BUT your current config is DEFAULT (see server logs -- it's store different settings from your recommendations at #586). From your logs: server works fine but start to disconnecs after 5 minutes. It's can be too many users online and too low server settings.

@jeffwadsworth

This comment has been minimized.

Copy link
Contributor

jeffwadsworth commented Jan 12, 2019

Is this still happening?

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Jan 12, 2019

Need more people to test... 30 online play without disconnects.

@JayDi85

This comment has been minimized.

Copy link
Member Author

JayDi85 commented Jan 16, 2019

New v33 works fine. I'm founded the disconnects reason -- server's start script don't copy original config on new version install and uses default one from ...neu1 folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.