[SPIGOT-2431] Console mass spammed with error Created: 20/Jun/16  Updated: 24/Jul/18  Resolved: 20/Jun/16

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Semaphorism Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: 1.10, spigot
Environment:

Ubuntu Server 16.04 (64bit)
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode)


 Description   

After starting the server, upon pinging the server (Seeing if its online), the server severely spams errors to the point it created a 700 MB log file (Yes, MB) in about 5 seconds from an empty log at the start.

The error(s) were this

Error

java.lang.RuntimeException: Unable to access address of buffer
at io.netty.channel.epoll.Native.read(Native Method) ~[spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.doReadBytes(EpollSocketChannel.java:678) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollInReady(EpollSocketChannel.java:714) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe$3.run(EpollSocketChannel.java:755) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:268) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at java.lang.Thread.run(java.base@9-internal/Thread.java:804) [?:?]
[22:38:22] Netty Epoll Server IO #1/WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

 Comments   
Comment by md_5 [ 24/Jul/18 ]

This issue was caused by using java 9 with spigot 1.10.

Since java 9 was not released at the time spigot didn't support it.

Only 1.12 and later support java 9.

Comment by Lorenzo Lapucci [ 24/Jul/18 ]

This issue has been marked as invalid and will not help you in resolving your issue Alikka, please open a new issue if you think that your problem is caused by Spigot and not by any plugin

Comment by Alikka - HUN [ 24/Jul/18 ]

it also writes to me
 

Comment by md_5 [ 20/Jun/16 ]

Java 9 is not a released Java version.

Generated at Tue Apr 22 05:22:28 UTC 2025 using Jira 10.3.5#10030005-sha1:190c783f2bd6c69cd5accdb70f97e48812a78d14.