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

2.5.22294: UnifiedInvocationHandler#invoke:58 - games.strategy.engine.GameOverException #13174

Open
tripleabuilderbot opened this issue Feb 13, 2025 · 0 comments
Labels
Error Report Issue reported via the in-game error reporter

Comments

@tripleabuilderbot
Copy link
Contributor

Map

world_war_ii_v3

Log Message

Unrecognized error occurred. If this is a repeatable error, please make a copy of this savegame and report to:
https://github.com/triplea-game/triplea/issues/new

TripleA Version

2.5.22294

Java Version

11.0.6

Operating System

Windows 10

Memory

Heap utilization statistics [MB]
Used Memory: 150
Free memory: 248
Total memory: 399
Max memory: 2048

Stack Trace

Exception: java.lang.RuntimeExceptionException on remote
java.lang.Exception
	at games.strategy.engine.message.UnifiedInvocationHandler.invoke(UnifiedInvocationHandler.java:58)
	at games.strategy.engine.framework.$Proxy37.startPlayerStep(Unknown Source)
	at games.strategy.engine.framework.ServerGame.waitForPlayerToFinishStep(ServerGame.java:544)
	at games.strategy.engine.framework.ServerGame.runStep(ServerGame.java:407)
	at games.strategy.engine.framework.ServerGame.startGame(ServerGame.java:297)
	at games.strategy.engine.framework.startup.launcher.ServerLauncher.launchInternal(ServerLauncher.java:173)
	at java.base/java.lang.Thread.run(Thread.java:834)


Exception: games.strategy.engine.GameOverExceptionGame Over Exception!
java.lang.Exception
	at games.strategy.engine.player.DefaultPlayerBridge$GameOverInvocationHandler.invoke(DefaultPlayerBridge.java:160)
	at com.sun.proxy.$Proxy17.getBattles(Unknown Source)
	at games.strategy.triplea.TripleAPlayer.battle(TripleAPlayer.java:500)
	at games.strategy.triplea.TripleAPlayer.start(TripleAPlayer.java:151)
	at games.strategy.engine.framework.ClientGame.lambda$new$0(ClientGame.java:175)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at games.strategy.engine.message.unifiedmessenger.EndPoint.invokeSingle(EndPoint.java:136)
	at games.strategy.engine.message.unifiedmessenger.EndPoint.lambda$invokeMultiple$0(EndPoint.java:120)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at games.strategy.engine.message.unifiedmessenger.EndPoint.invokeMultiple(EndPoint.java:121)
	at games.strategy.engine.message.unifiedmessenger.EndPoint.invokeLocal(EndPoint.java:111)
	at games.strategy.engine.message.unifiedmessenger.UnifiedMessenger.lambda$processMessage$0(UnifiedMessenger.java:321)
	at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)


@tripleabuilderbot tripleabuilderbot added the Error Report Issue reported via the in-game error reporter label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Error Report Issue reported via the in-game error reporter
Projects
None yet
Development

No branches or pull requests

1 participant