Help Console Error

[mikelolos]

Hello to all members today my console shows this error all the time and i dont know why...

 

 

Exception in thread "General Pool-1" java.lang.NullPointerException

        at java.util.concurrent.ConcurrentHashMap.hash<Unknown Source>

        at java.util.concurrent.ConcurrentHashMap.remove<Unknown Source>

        at com.l2jfrozen.gameserver.thread.LoginServerThread.sendLogout<LoginServ

verThread.java:510>

        at com.l2jfrozen.gameserver.network.L2GameClient$DisconnectTask.run<L2Ga

meClient.java:1032>

        at java.util.concurrent.ThreadPoolExecutor.runWorker<Unknown Source>

        at java.util.concurrent.ThreadPoolExecutor$Worker.run<Unknown Source>

        at java.lang.Tread.run<Unknown Source>

        

 

and this message is continued wth   "General Pool-3"   "General Pool-7" all the time..

 

any help pliz?what is this?ty in advance....

[Tryskell]

sendLogout<LoginServverThread.java:510>

 line ?

 

[mikelolos]

line 510   _accountsInGameServer.remove(account);

 

 

line 1032 LoginServerThread.getInstance().sendLogout(L2GameClient.this.getAccountName());

 

 

i cannot undestund how the error come up i run test beta many days and now after 1 restart and no code changes i have this..ty in advance

 

i have see in login console some warnings about bruteforce is possible someone did something bad ?

Edited October 18, 2015 by mikelolos

[Tryskell]

Not really helpful, sorry. You should take latest rev you miss at least 20 lines.

 

If you got only one error, don't bother, otherwise... I don't know.

[mikelolos]

it is possible this error have to do something with the database ?i found 1 backup of the server that is 3 months ago...all the server folder configs/lib everything and i run it and i have the same error !!!! and the error is 2 days old so what is causing the error?ty again people... 

[Tryskell]

Until you manually edit your database to fuck up an account, normally no. If you got the same error with a working, 3 months old backup, it only means it's not a database problem.

 

In your case it would be more helpful to get a 3 month old SVN and revert to a previous revision  :dat: