|
From: SourceForge.net <no...@so...> - 2012-06-05 14:22:49
|
Bugs item #3531906, was opened at 2012-06-04 07:00 Message generated for change (Comment added) made by robeden You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=424682&aid=3531906&group_id=39235 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Next Minor Release >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: ArrayIndexOutOfBoundsException in IndexHashed Initial Comment: Well in our project we use trove 3.0.2 for now and we got below AIOOB. If you need futher explaining regarding this I am willing to to do via email can email me at to...@bl... 02:31:58 [ERROR] Error on calculating rewards for Attackable Fervent Kanabion java.lang.ArrayIndexOutOfBoundsException: 88 at gnu.trove.impl.hash.TIntHash.indexRehashed(TIntHash.java:233) ~[trove-3.0.2.jar:3.0.2] at gnu.trove.impl.hash.TIntHash.index(TIntHash.java:219) ~[trove-3.0.2.jar:3.0.2] at gnu.trove.impl.hash.TIntHash.contains(TIntHash.java:163) ~[trove-3.0.2.jar:3.0.2] at gnu.trove.map.hash.TIntObjectHashMap.containsKey(TIntObjectHashMap.java:181) ~[trove-3.0.2.jar:3.0.2] at com.l2dc.gameserver.model.actor.knownlist.ObjectKnownList.knowsObject(ObjectKnownList.java:123) ~[l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Attackable.calculateRewards(L2Attackable.java:900) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Character.doDie(L2Character.java:2703) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Npc.doDie(L2Npc.java:1621) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Attackable.doDie(L2Attackable.java:650) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.instance.L2MonsterInstance.doDie(L2MonsterInstance.java:338) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.status.CharStatus.reduceHp(CharStatus.java:249) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.status.NpcStatus.reduceHp(NpcStatus.java:58) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.status.AttackableStatus.reduceHp(AttackableStatus.java:56) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Character.reduceCurrentHp(L2Character.java:9450) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Attackable.reduceCurrentHp(L2Attackable.java:612) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.L2Attackable.reduceCurrentHp(L2Attackable.java:542) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.task.chartasks.HitTask.onHitTimer(HitTask.java:210) [l2dcserver.jar:na] at com.l2dc.gameserver.model.actor.task.chartasks.HitTask.run(HitTask.java:66) [l2dcserver.jar:na] at com.l2dc.gameserver.ThreadPoolManager$RunnableWrapper.run(ThreadPoolManager.java:97) [l2dcserver.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_04] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [na:1.7.0_04] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [na:1.7.0_04] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_$ at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [na:1.7.0_04] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.7.0_04] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.7.0_04] ---------------------------------------------------------------------- >Comment By: Rob Eden (robeden) Date: 2012-06-05 07:22 Message: This was a usage problem. ---------------------------------------------------------------------- Comment By: Rob Eden (robeden) Date: 2012-06-04 15:05 Message: Sent this email: -------------------------- Hello - In regard to your bug (quoted below), I'll need more information regarding the environment and a test case would be very helpful. Does this error happen all the time? Frequently? Rarely? etc... I can say that I exercise this code often without issue. The most likely cause of this error is generally that it's being done in a threaded environment without adequate thread safety. Try wrapping the maps in TCollections.synchronizedMap(...) and see if that helps. For now the bug will be put into PENDING state and will automatically close if no further comments are made within 10 days. Please reply to this email or comment on the bug with additional details. Thanks! Rob -------------------------- Putting bug into PENDING state. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=424682&aid=3531906&group_id=39235 |