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

Netty 4.1.0.Final Not Working #286

Closed
garantiertnicht opened this issue Jun 5, 2016 · 10 comments
Closed

Netty 4.1.0.Final Not Working #286

garantiertnicht opened this issue Jun 5, 2016 · 10 comments

Comments

@garantiertnicht
Copy link

I downloaded the binary and scorce code, and the versions from the last commit do not work. Instantly after connecting the client and the server shows up that I lost connection and the connection will be closed. Neither the console or the log are giving some useful information, but changing the netty version back seems to resolve the problem.

Nothing interesting, but her's the console output:
20:35:01 [INFORMATION] garantiertnicht [/0:0:0:0:0:0:0:1:51404] connected, UUID: 1f4f35f5-b916-4ee6-83a8-9044ae3b00f2
20:35:01 [INFORMATION] garantiertnicht joined the game
20:35:01 [INFORMATION] garantiertnicht [/0:0:0:0:0:0:0:1:51404] lost connection
20:35:01 [INFORMATION] garantiertnicht left the game

@mastercoms
Copy link
Member

I will see what netty did. Maybe I shouldn't have assumed a release version of a popular network library would be stable.

@mastercoms
Copy link
Member

I reverted back to CR7 for now. I will upgrade to final once I figure out the issue.

@mastercoms mastercoms self-assigned this Jun 6, 2016
@mastercoms mastercoms changed the title Can't connect with netty 4.1.0.Final, but .CR7 works just fine Netty 4.1.0.Final Not Working Jun 6, 2016
@mastercoms mastercoms added this to the 2016Q2 milestone Jun 7, 2016
@mastercoms
Copy link
Member

The problem is not the switch to PooledByteBufAllocator.

Also, it seems like the connection is randomly dropping. Sometimes the client can send some packets before disconnecting, and very rarely can connect.

@aramperes aramperes removed this from the 2016Q3 milestone Jan 7, 2017
@gdude2002 gdude2002 added this to In Progress in March 2017 Feb 27, 2017
@gdude2002 gdude2002 moved this from In Progress to Backlog in March 2017 Feb 27, 2017
@gdude2002 gdude2002 moved this from Backlog to Stalled in March 2017 Feb 27, 2017
@mastercoms mastercoms added this to the 2017.3 milestone Mar 4, 2017
@mastercoms mastercoms moved this from Stalled (Little activity since '16) to In Progress in March 2017 Mar 9, 2017
@gdude2002 gdude2002 added this to Backlog in April 2017 Apr 1, 2017
@gdude2002 gdude2002 removed this from In Progress in March 2017 Apr 1, 2017
@satoshinm
Copy link
Contributor

Netty has since updated to 4.1.9 (10-Mar-2017), I am using it in another project seems stable, is this still a problem with the latest version?

@mastercoms
Copy link
Member

Yes, this is still a problem with 4.1.9.Final.

@mastercoms
Copy link
Member

Closed in 1999ea5.

@ghost ghost removed the help wanted label Apr 13, 2017
@mastercoms
Copy link
Member

Reopening because 199ea5 was reverted due to some regressions in 73228f1.

@mastercoms mastercoms reopened this Apr 16, 2017
@gdude2002 gdude2002 removed this from Backlog in April 2017 May 4, 2017
@gdude2002 gdude2002 added this to Backlog in May 2017 May 4, 2017
@picknchew
Copy link
Member

picknchew commented May 9, 2017

Seems to be an issue with the current version.
I managed to produce a stacktrace. Unsure if related:

com.flowpowered.network.exception.ChannelClosedException: Trying to send a message when a session is inactive!
        at com.flowpowered.network.session.BasicSession.sendWithFuture(BasicSession.java:89)
        at net.glowstone.net.GlowSession.sendWithFuture(GlowSession.java:393)
        at com.flowpowered.network.session.BasicSession.send(BasicSession.java:103)
        at net.glowstone.entity.GlowPlayer.sendAbilities(GlowPlayer.java:1268)
        at net.glowstone.entity.GlowPlayer.setAllowFlight(GlowPlayer.java:1225)
        at net.glowstone.entity.GlowPlayer.setGameModeDefaults(GlowPlayer.java:1166)
        at net.glowstone.entity.GlowPlayer.join(GlowPlayer.java:355)
        at net.glowstone.net.GlowSession.setPlayer(GlowSession.java:360)
        at net.glowstone.net.handler.login.EncryptionKeyResponseHandler$ClientAuthCallback.lambda$done$0(EncryptionKeyResponseHandler.java:153)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at net.glowstone.scheduler.GlowTask.run(GlowTask.java:167)
        at net.glowstone.scheduler.GlowScheduler.pulse(GlowScheduler.java:152)
        at net.glowstone.scheduler.GlowScheduler.lambda$start$0(GlowScheduler.java:83)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)```

@mastercoms
Copy link
Member

Related. The way we were using idle detection is broken on later versions, we have to find a workaround for it.

@aramperes aramperes removed this from the 2017.3 milestone Jul 8, 2017
@mastercoms
Copy link
Member

Fixed in 43a1f78.

@ghost ghost removed the help wanted label Dec 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
May 2017
Backlog
Development

No branches or pull requests

6 participants