Help L2Character$Notifyaitask

[Xerus]

 com.l2jesios.gameserver.model.actor.L2Character$NotifyAITask run

WARNING: 

java.lang.StackOverflowError

 at com.l2jesios.gameserver.ai.L2CharacterAI.maybeMoveToPawn(L2CharacterAI.java:934)

 at com.l2jesios.gameserver.ai.L2PlayerAI.thinkCast(L2PlayerAI.java:240)

 at com.l2jesios.gameserver.ai.L2PlayerAI.onEvtThink(L2PlayerAI.java:316)

 at com.l2jesios.gameserver.ai.L2CharacterAI.onEvtArrived(L2CharacterAI.java:673)

 at com.l2jesios.gameserver.ai.AbstractAI.notifyEvent(AbstractAI.java:417)

 at com.l2jesios.gameserver.ai.AbstractAI.notifyEvent(AbstractAI.java:340)

 at com.l2jesios.gameserver.model.actor.L2Character.moveToLocation(L2Character.java:3893)

 at com.l2jesios.gameserver.model.actor.L2Character$AIAccessor.moveTo(L2Character.java:3039)

 at com.l2jesios.gameserver.ai.AbstractAI.moveTo(AbstractAI.java:582)

 at com.l2jesios.gameserver.ai.AbstractAI.moveToPawn(AbstractAI.java:538)

 at com.l2jesios.gameserver.ai.L2CharacterAI.maybeMoveToPawn(L2CharacterAI.java:948)

 

This error is flloding my gs very often and produce lag anyone know how to fix it? this is the line in L2CharacterAI

 

protected boolean maybeMoveToPawn(L2Object target, int offset)
{
if (target == null || offset < 0) // skill radius -1
return false;


offset += _actor.getTemplate().getCollisionRadius();   //this is the line 934
if (target instanceof L2Character)
offset += ((L2Character) target).getTemplate().getCollisionRadius();

 

[Akken]

L2jEsios, really.. ? :not bad:

 

It's 'kinda' outdated, don't you think? :P

since he has sources :P nothing to worry about and he owns a pvp server so he pays he fix he implement and such

[SweeTs]

since he has sources :P nothing to worry about and he owns a pvp server so he pays he fix he implement and such

It's based on aCis 290 rev, you still think that there is nothing to worry about..? :D

[Akken]

It's based on aCis 290 rev, you still think that there is nothing to worry about..? :D

well i am worried now :P

[Xerus]

L2jEsios, really.. ? :not bad:

 

It's 'kinda' outdated, don't you think? :P

Not if you are working on it for 5 months, anyway i am seeing the error again but i cant see it in the logs files why?

[Akken]

Not if you are working on it for 5 months, anyway i am seeing the error again but i cant see it in the logs files why?

if you followed versus method well obviously the fix you applied it was not a fix but you prevent from see it on log files readd old code back.. the error isnt the exception message log, you wont fix it buy deleting the message on logs on console.. if you even delete the log of gs console you will still got the lag and the error .. it is obviously a failure of a code inside the characteraitask

Edited December 10, 2013 by Akken

[Xerus]

if you followed versus method well obviously the fix you applied it was not a fix but you prevent from see it on log files readd old code back.. the error isnt the exception message log, you wont fix it buy deleting the message on logs on console.. if you even delete the log of gs console you will still got the lag and the error .. it is obviously a failure of a code inside the characteraitask

I am not a newbie dude rofl... irony?

[Akken]

I am not a newbie dude rofl... irony?

dah.. i am outta here i hope someone give you the fix 

[xdem]

This happens on the dedicated machine or your home? stackoverflows are thrown like outofmemory error so try increasing JVM heap... Also look at the run task to see how often this Runnable is called, another reason would be badcoded codes in L2Character causeing unlimited loops or ungarbagable variables?

[Versus]

if you followed versus method well obviously the fix you applied it was not a fix but you prevent from see it on log files readd old code back.. the error isnt the exception message log, you wont fix it buy deleting the message on logs on console.. if you even delete the log of gs console you will still got the lag and the error .. it is obviously a failure of a code inside the characteraitask

Yeah, i was at work this morning, without looking at source and seeing this thoroughly, i remembered that at old L2J revs Throwable was used everywhere, so i recommended him to change that (which he should nevertheless).

 

Stack overflows are usually caused by bad recursive calls. Most likely, a recursive call without a proper termination condition.

@OP we can't help you much here, we'd need sources in order to provide further help.

[Xerus]

This happens on the dedicated machine or your home? stackoverflows are thrown like outofmemory error so try increasing JVM heap... Also look at the run task to see how often this Runnable is called, another reason would be badcoded codes in L2Character causeing unlimited loops or ungarbagable variables?

This is on my dedicated server.. ram is not a problem for sure cause it has 16 gb just for the server and the rest to the operating system.

 

Btw i will pay anyone who will fix this for me

[xdem]

This is on my dedicated server.. ram is not a problem for sure cause it has 16 gb just for the server and the rest to the operating system.

 

Btw i will pay anyone who will fix this for me

 

I didnt asked you for the dedi ram mr "not-newbie", JVM alocates memory upon it's initiliazation, u can change it at the .bat

[Xerus]

I didnt asked you for the dedi ram mr "not-newbie", JVM alocates memory upon it's initiliazation, u can change it at the .bat

Yep dude. My dedi has 32 gb ram.. in the bat i set it to 16gb

[MWZ]

Yep dude. My dedi has 32 gb ram.. in the bat i set it to 16gb

 

Make sure you are using 64 bits JVM, otherwise, the 32GB ram are useless.

[Xerus]

Make sure you are using 64 bits JVM, otherwise, the 32GB ram are useless.

What do u mean 64 bits jvm ? Are u talking about os?

[MWZ]

What do u mean 64 bits jvm ? Are u talking about os?

 

Java, make sure you are using the 64 bits version.