PreciousStones

PreciousStones

269k Downloads

[WARNING] Could not properly handle event CHUNK_LOAD

pilotdan1985 opened this issue ยท 2 comments

commented

I set up 2 custom ps stones last night. Today I started having a ton of java errors. The two stones I created are these:

  • title: Market Area
    block: '98:3'
    limits:
    • 1
    • 2
    • 4
      radius: 30
      cuboid: true
      custom-height: 20
      price: 2000
      prevent-fire: true
      prevent-flow: true
      prevent-place: true
      prevent-destroy: true
      prevent-explosions: true
      prevent-pvp: true
      prevent-mob-damage: true
      welcome-message: true
      farewell-message: true
      visualize-on-place: true
      dynmap-area: true
      mixing-group: 5
  • title: Market Stall
    block: '98:2'
    radius: 5
    cuboid: true
    prevent-fire: true
    prevent-flow: true
    prevent-place: true
    prevent-destroy: true
    prevent-explosions: true
    prevent-pvp: true
    prevent-mob-damage: true
    visualize-on-place: true
    mixing-group: 5
    plot: true
    buyable: true
    rentable: true
    allowed-only-inside:
    • Market Area

It worked almost perfectly last night. I say almost perfectly because the "market stall" block had a minor glitch on being clicked by the owner that the visualization wont go away until they relog. I figure it was no big deal. Today, I started to get a ton of java errors and crashing peoples clients, as well as the entire server. Here is one error: (there is a second error that I have see after this one: I was using the beta 205 release when the first error occured. I just disabled that one and re-installed the latest release here: http://dev.bukkit.org/server-mods/preciousstones/files/140-9-5-4/

[code]2013-01-23 14:43:42 [WARNING] Could not properly handle event CHUNK_LOAD:
java.lang.IllegalAccessError: Synchronized code got accessed from another thread: java.util.concurrent.ThreadPoolExecutor$Worker
at org.bukkit.event.NLTCListener.onChunkLoad(NLTCListener:0)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462)
at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:139)
at net.timedminecraft.server.TimedChunkProviderServer.getChunkAt(TimedChunkProviderServer.java:153)
at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:85)
at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getChunkAt(CraftWorld.java:115)
at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getBlockAt(CraftWorld.java:79)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.AbstractVec.getBlock(AbstractVec.java:172)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.Field.getAttachedFieldSign(Field.java:2437)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.Field$Update.run(Field.java:2688)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2013-01-23 14:43:42 [INFO] This error is logged only once: it could have occurred multiple times by now.
2013-01-23 14:43:42 [INFO] Potential failures may occur in other plugins handling this Event.
2013-01-23 14:43:42 [INFO] Please contact one of the authors of plugin 'PreciousStones': Phaed[/code]

[code]2013-01-23 15:33:10 [WARNING] Could not properly handle event CHUNK_LOAD:
java.lang.IllegalAccessError: Synchronized code got accessed from another thread: java.util.concurrent.ThreadPoolExecutor$Worker
at org.bukkit.event.NLTCListener.onChunkLoad(NLTCListener:0)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462)
at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:139)
at net.timedminecraft.server.TimedChunkProviderServer.getChunkAt(TimedChunkProviderServer.java:153)
at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:85)
at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getChunkAt(CraftWorld.java:115)
at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getBlockAt(CraftWorld.java:79)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.AbstractVec.getBlock(AbstractVec.java:172)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.Field.getAttachedFieldSign(Field.java:2437)
at net.sacredlabyrinth.Phaed.PreciousStones.vectors.Field$Update.run(Field.java:2688)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2013-01-23 15:33:10 [INFO] This error is logged only once: it could have occurred multiple times by now.
2013-01-23 15:33:10 [INFO] Potential failures may occur in other plugins handling this Event.
2013-01-23 15:33:10 [INFO] Please contact one of the authors of plugin 'PreciousStones': Phaed[/code]

commented

I have restored a backup of the config from 1/15/13 and it didnt fix anything... so its not the config. Maybe it has something to do with some of the flags that were applied to the new ps stones?

commented

This is fixed on latest build.