Thread lock with AFK time? #520

  • Defect
  • Replied
Assigned to _ForgeUser8455416
  • _ForgeUser7707380 created this issue Oct 21, 2014

    NOTE: If you supply copies of your .yml or console log files, please use pastebin, dropbox, or other service and provide link,  instead of copy/paste of the file into this report. Thanks!

    What Version of OnTime and Bukkit are you using?
    OnTime: 3.13.4
    Bukkit: 1.6.4

    What storage option are you using? (YML or MYSQL) ? mysql

    What permissions plugin are you using? (Groupmanager, PEX,bPermissions, etc.) pex

    Please provide a link to a copy of your plugins/OnTime/config.yml:

    What steps will reproduce the problem?
    1. Unsure just happened randomly, not the first time either.

    What is the expected output? What do you see instead?

    Do you have an console log of what happened?

    Are you having a "rewards" problem?  Please provide a link to a copy of your /plugins/OnTime/rewards.yml :

    Did you turn on OnTime logging (/ontime logfile enable 1)?  If so, provide a link to that file too.

    Please provide any additional information below.

    Thread dump here:

  • _ForgeUser7707380 added the tags New Defect Oct 21, 2014
  • _ForgeUser7707380 edited description Oct 21, 2014
  • _ForgeUser8455416 posted a comment Oct 27, 2014

    This is an interesting issue. The point that your sever is getting hung up is during a call/execution of a standard JAVA (hashing) function call. There is nothing unique that OnTime is doing with its hash tables, so I am not sure where even to begin an investigation.

    2014-10-21 19:12:14 [SEVERE]            java.util.HashMap.getEntry(
    2014-10-21 19:12:14 [SEVERE]            java.util.HashMap.containsKey(
    2014-10-21 19:12:14 [SEVERE]            me.edge209.OnTime.AwayFK.notAFK(

    Have you raised this issue with Cauldron, and they have already dismissed it as a plugin issue?

    To further make this a mystery, the piece of OnTime code that is indicated in these log files has not been touched in more than a year's time, with thousands of copies of OnTime downloaded with this exact code, yet this is the first report of this type I have seen.

    I will go and poke around in that code and see if there is anything I can do to at least catch the lockup before it becomes a problem, but at this point I am not very optimistic that I am going to be able to come up with anything.

  • _ForgeUser8455416 removed a tag New Oct 27, 2014
  • _ForgeUser8455416 added a tag Waiting Oct 27, 2014
  • _ForgeUser7707380 posted a comment Oct 28, 2014

    @Edge209: Go

    Thanks for your response, I have not raised this with Cauldron and will do so now. The issue has happened a few time times now on seperate servers, I want to say this only started after updating to 3.13.4 from 3.13.3 but I can't be certain.

  • _ForgeUser7707380 removed a tag Waiting Oct 28, 2014
  • _ForgeUser7707380 added a tag Replied Oct 28, 2014
  • _ForgeUser7707380 posted a comment Nov 17, 2014

    Fyi the issue was closed on Cauldron side stating there wasnt any cause there. Just to add a bit more information I have been running Ontime for several weeks now on 3 1.7.10 servers without this crash occurring so it looks to be isolated to 1.6.4 which I'm guessing is no longer supported.

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