-
Bug
-
Resolution: Works As Intended
-
None
-
1.18.2
-
None
-
Confirmed
-
Networking
The Bug:
The game output console is logged with various errors and warnings whilst playing realms, having previously played realms, or sitting on the title screen.
Below are some examples of the errors and warnings that were logged into the game output console.
[19:06:58] [pool-3-thread-1/ERROR]: Couldn't get pending invite count dvm: Could not connect to Realms: Read timed out at dub.a(SourceFile:438) ~[1.18.2.jar:?] at dub.k(SourceFile:326) ~[1.18.2.jar:?] at dub.j(SourceFile:321) ~[1.18.2.jar:?] at dvq.q(SourceFile:217) ~[1.18.2.jar:?] at dwx.run(SourceFile:32) [1.18.2.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
[16:16:47] [pool-3-thread-1/ERROR]: Couldn't get server list dvm: Could not connect to Realms: Read timed out at dub.a(SourceFile:438) ~[1.18.2.jar:?] at dub.e(SourceFile:153) ~[1.18.2.jar:?] at dvq.p(SourceFile:200) ~[1.18.2.jar:?] at dwx.run(SourceFile:32) [1.18.2.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
[19:40:16] [pool-3-thread-1/ERROR]: Couldn't get live stats dvm: Could not connect to Realms: Read timed out at dub.a(SourceFile:438) ~[1.18.2.jar:?] at dub.f(SourceFile:171) ~[1.18.2.jar:?] at dvq.s(SourceFile:235) ~[1.18.2.jar:?] at dwx.run(SourceFile:32) [1.18.2.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
[10:25:01] [pool-3-thread-2/ERROR]: Couldn't get trial availability dvm: Could not connect to Realms: Read timed out at dub.a(SourceFile:438) ~[1.18.2.jar:?] at dub.n(SourceFile:382) ~[1.18.2.jar:?] at dvq.r(SourceFile:226) ~[1.18.2.jar:?] at dwx.run(SourceFile:32) [1.18.2.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
[19:18:01] [pool-3-thread-3/WARN]: Failed fetching news from Realms, falling back to local cache dvm: Could not connect to Realms: Read timed out at dub.a(SourceFile:438) ~[1.18.2.jar:?] at dub.m(SourceFile:371) ~[1.18.2.jar:?] at dvq.u(SourceFile:258) ~[1.18.2.jar:?] at dvq.t(SourceFile:244) ~[1.18.2.jar:?] at dwx.run(SourceFile:32) [1.18.2.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
Steps to Reproduce:
- Launch an instance of the latest release with logs enabled.
- Join a realm and simply just play around for ten minutes or so.
- Look at the game output console.
- Take note as to whether or not the game output console is logged with various errors and warnings whilst playing realms, having previously played realms, or sitting on the title screen.
Observed Behavior:
Errors and warnings are printed into the game output console.
Expected Behavior:
No errors and warnings would be printed into the game output console.
- is duplicated by
-
MC-250195 logs spammed with realms error messages when playing singleplayer
- Resolved