ArrayOutOfBounds when updateCheck() fails #98


  • New
  • Defect
Open
Assigned to _ForgeUser8106975
  • _ForgeUser7288038 created this issue Mar 12, 2013

    12.03 09:37:39 [Server] INFO at net.minecraft.server.v1_4_R1.ThreadServerApplication.run(SourceFile:849)
    12.03 09:37:39 [Server] INFO at net.minecraft.server.v1_4_R1.MinecraftServer.run(MinecraftServer.java:427)
    12.03 09:37:39 [Server] INFO at net.minecraft.server.v1_4_R1.MinecraftServer.q(MinecraftServer.java:494)
    12.03 09:37:39 [Server] INFO at net.minecraft.server.v1_4_R1.DedicatedServer.r(DedicatedServer.java:224)
    12.03 09:37:39 [Server] INFO at net.minecraft.server.v1_4_R1.MinecraftServer.r(MinecraftServer.java:530)
    12.03 09:37:39 [Server] INFO at org.bukkit.craftbukkit.v1_4_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:344)
    12.03 09:37:39 [Server] INFO at org.bukkit.craftbukkit.v1_4_R1.scheduler.CraftTask.run(CraftTask.java:53)
    12.03 09:37:39 [Server] INFO at se.troed.plugin.Courier.Courier$2.run(Courier.java:259)
    12.03 09:37:39 [Server] INFO java.lang.ArrayIndexOutOfBoundsException: 1
    12.03 09:37:39 [Server] WARNING Task #55 for Courier v1.1.9 generated an exception
    12.03 09:37:39 [Server] WARNING Caught an exception in updateCheck()

    That is the error, and it wasn't happening until a few days ago. I have been using Courier v 1.1.9 and CB 1.4.7 R1.0 since R1.0 came out and never had problems. But this error has been coming up occasionally now, and sometimes players get kicked from the game because of it.

  • _ForgeUser7288038 added the tags New Defect Mar 12, 2013
  • _ForgeUser8106975 posted a comment Mar 12, 2013

    Thanks,

    My guess is it's due to BukkitDev sometimes timing out when Courier checks to see if there's a new version and a bug on my part in Courier when that happens. However, I don't understand how come a player could get kicked because of it since the exception is in the update thread only.

    Anyway, there's an easy workaround: Just disable the automatic update checking by setting the interval to 0 in the Courier config file. You'll just have to remember checking for new versions here manually :)

    Renaming this bug report to better indicate the actual error which is in how the return value from updateCheck() is handled when an exception has been thrown compared to the normal flow:

    https://github.com/troed/Courier/blob/master/src/se/troed/plugin/Courier/Courier.java


To post a comment, please login or register a new account.