Are there any Java Server-side tokens to limit iterations?

#1

Hi

I’ve just started and would like to know if anyone else is facing the issue of Java exiting from server-side. From a brief glnce at the logs, the problem appears to be caused in MALMO on running out of tokens. Is there a way to increase the number of tokens? They seem to get depleted 1 per 20 iterations

There’s a reference to “run out of time” on the docs, but the context feels wrong…

Now let’s take actions through the environment until time runs out or the agent dies.

The segregated logs of the error are:

[23:24:07] [Server thread/INFO]: [STDOUT]: >>>> MineRLAgent
[23:24:07] [Client thread/INFO]: [STDOUT]: ***Telling server we are ready - MineRLAgent
[23:24:08] [Client thread/INFO]: [STDOUT]: ***Telling server we are ready - MineRLAgent
[23:24:08] [Client thread/INFO]: [STDOUT]: CLIENT request state: RUNNING
[23:24:08] [Client thread/INFO]: [STDOUT]: CLIENT enter state: RUNNING
[23:24:08] [Server thread/INFO]: [STDOUT]: SERVER request state: RUNNING
[23:24:08] [Server thread/INFO]: [STDOUT]: SERVER enter state: RUNNING
[23:24:08] [Client thread/INFO]: [STDOUT]: Resized the window
[23:24:08] [Client thread/INFO]: [STDOUT]: Unpausing
[23:24:08] [Client thread/INFO]: [CHAT] §l300...
[23:24:09] [Server thread/INFO]: [STDOUT]: Warning: managed 15/20 ticks this second.
[23:24:09] [Client thread/INFO]: [CHAT] §l299...
[23:24:09] [Client thread/INFO]: [CHAT] §l298...
[23:24:10] [Client thread/INFO]: [CHAT] §l297...

.
.
.
...
[23:25:21] [Client thread/INFO]: [CHAT] §c§l4...
[23:25:21] [Client thread/INFO]: [CHAT] §c§l3...
[23:25:22] [Client thread/INFO]: [CHAT] §c§l2...
[23:25:22] [Client thread/INFO]: [CHAT] §c§l1...
[23:25:22] [Server thread/INFO]: [STDOUT]: SERVER request state: CLEAN_UP
[23:25:22] [Server thread/INFO]: [STDOUT]: SERVER enter state: CLEAN_UP
[23:25:22] [Server thread/INFO]: [STDOUT]: SERVER request state: DORMANT
[23:25:22] [Client thread/INFO]: [CHAT] §c§l0...
[23:25:22] [Server thread/INFO]: [STDOUT]: SERVER enter state: DORMANT
[23:25:23] [EnvServerSocketHandler/INFO]: Java has been asked to exit (code 0) by net.minecraftforge.fml.common.FMLCommonHandler.exitJava(FMLCommonHandler.java:659).

Environment is docker, headless with a VNC + xvfb and latest minerl from pip.