AL-262/268 SM_CHARACTER_LIST error for one account
Hi all,
Using AL-262 for some reason an account cannot login. It errors out after the agreement page (you have been disconnected). Game Server Log shows this:
22:31:10.685 ERROR[ReadWrite-0 Dispatcher]: - Dispatcher error! java.lang.Negati
veArraySizeException
java.lang.NegativeArraySizeException: null
at com.aionlightning.gameserver.network.aion.PlayerInfo.writePlayerInfo(
PlayerInfo.java:163) ~[AL-Game.jar:na]
at com.aionlightning.gameserver.network.aion.serverpackets.SM_CHARACTER_
LIST.writeImpl(SM_CHARACTER_LIST.java:66) ~[AL-Game.jar:na]
at com.aionlightning.gameserver.network.aion.AionServerPacket.write(Aion
ServerPacket.java:79) ~[AL-Game.jar:na]
at com.aionlightning.gameserver.network.aion.AionConnection.writeData(Ai
onConnection.java:250) ~[AL-Game.jar:na]
at com.aionlightning.commons.network.Dispatcher.write(Dispatcher.java:28
5) ~[al-commons-4.3.jar:na]
at com.aionlightning.commons.network.AcceptReadWriteDispatcherImpl.dispa
tch(AcceptReadWriteDispatcherImpl.java:81) ~[al-commons-4.3.jar:na]
at com.aionlightning.commons.network.Dispatcher.run(Dispatcher.java:103)
~[al-commons-4.3.jar:na]
22:31:10.694 INFO [pool-5-thread-1]: - Sending account disconnected 6.
Loading previous server version up (same database, cant remember version), the account loads fine. This account worked earlier in the day on 262 without errors (just logged off). I tried moving the last used toon in a confirmed valid location within the DB but didn't help fix on 262 at all.
Several other accounts on there load just fine.
Thanks much for the help.
- - - Updated - - -
EDIT: Doesnt work either with AL-268; same error.
Re: AL-262/268 SM_CHARACTER_LIST error for one account
Ok this one is best solved by process of elimination in the players table of the GS DB (through Navicat). You'll have to find each character the account has, delete the row corresponding to each toon (make sure you do a backup), save it, and test logon. This does not require a restart of the server. As mentioned in the 4.0 thread somewhere, it is most likely some value that java doesn't like on that row for the character.