Problems with new GameServer

[Nocto]

hi,

i have a problem with the new gameserver (crafting addition) - after a while it seems that the chars could not be saved...
i get this "Parrallelitätsverletzung" (ConcurrencyException) ...

Code: Select all

[color=#FF0000][b]
Error updating table DOLCharacters: Parallelitätsverletzung : Der UpdateCommand hat sich auf 0
Datensätze ausgewirkt.

10/28/2004 12:21:56 046 DOLCharacters_ID=d7a0fa74-73fe-444e-b540-52314b97c6f4 HasGravestone=False
GravestoneRegion=0 Constitution=45 Dexterity=112 Strength=40 Quickness=100 Intelligence=115 Piety=60
Empathy=60 Charisma=60 BountyPoints=0 RealmPoints=0 SkillSpecialtyPoints=2 RealmSpecialtyPoints=0
Experience=173505003824 MaxHealth=100 MaxMana=100 MaxEndurance=100 MaxConcentration=100 Health=566
Mana=315 Endurance=100 Concentration=100 ClassType=DOL.GS.GamePlayer AccountName=xxx
AccountSlot=24 CreationDate=02.08.2004 00:00:00 LastPlayed=28.10.2004 12:20:53 Name=Bubezleb LastName=
GuildName=Support Gender=0 Race=12 Level=50 Class=40 Realm=3 CreationModel=43333 Region=1 ActiveWeaponSlot=1
CurrentModel=43333 Xpos=470911 Ypos=630414 Zpos=1704 BindXpos=426617 BindYpos=416326 BindZpos=5712
BindRegion=51 BindHeading=912 DeathCount=0 Direction=2053
MaxSpeed=400 Copper=29 Silver=99 Gold=10 Platinum=0 Mithril=0 SerializedAbilities=
SerializedSpecs=Light|4;Mana|20;Void|50 Styles=
SerializedRealmAbilities= SerializedFriendsList= IsCloakHoodUp=True IsLevelSecondStage=False
FlagGuildName=False GuildRank=10 PlayedTime=102 DeathTime=[color=#00FF00]-
9223372036854775808 ???[/color] RespecAmountAllSkill=0 RespecAmountSingleSkill=0 SafetyFlag=True
10/28/2004 12:21:56 046 Affected columns: [/b][/color]

can someone tell me why this happens ?
and we have a problem with merchants on our shard, sometimes if we try to remove one i get an error that it could not be deletet because the heading does not fit into an int16, why does the server create headings like 65400 if maxheading is nearly 4600 or something ?

at the current version we have problems with mobs, they sometimes disappear, dunno why?! (maybe the respawn changes ? )

and at most merchants / trainers the equipment is missing, are there any changes to the equipment code ?

FletchingNPC keeps saying my Ranger that he "is not my master ?!"

thanks
Nocto

[Blue]

This is not a problem from crafter, its in there for a long time now. I saw that too.

[duff]

for your ranger and craft it is normal i have not finished!!!
it s in dev

[Nocto]

This is not a problem from crafter, its in there for a long time now. I saw that too.

we're running our server now for nearly 3 months, without any char saving problems, after this patch this EVERYTIMES happens after some minutes, and you wanna tell me that that is normal ?

for your ranger ...

aaah... np - so i'll test it with a (whats "dose" in english ?) albion char

[bstag]

i did latest cvs my self... have this issue the only changes logged in history are crafting and mysql stuff... which happens to me what me and nocto use. the issue seems to be with played time and deathtime... it looks like played time starts at 0 every log in...

so not long time now but 2 - 4 days now. last one I was runnig with out issue is this

Blue (24.oct.2004):
- Bugfix: Console does not block server when scrolling in console window


note this issue happens as soon as you log in and on a server running my sql detahtimes look freaking insane. and played looks to reset..
PlayedTime=145
DeathTime=-9223372036854775808

[nor]

DeathTime=-9223372036854775808

It's just long.MinValue if no deaths yet.

[Nocto]

well why was it set to NULL before ?
and now this ... long.MinValue ?

where can i find these changes to deactivate them and test if it works ?

[nor]

It was long.MinValue from the start, set in character table.

[bstag]

ohh cause i have not died huh... no that is not it i figured the clue would have come when i mentioned the playtime counter being reset to zero. my death time in the db is 139900 right now so how does it set to what you say is 0 when i just log in with the character.. and besides that the code for this calculation did not change as far as in the code what changed is what reads it out of the mysql database.


so what i am saying is i log in with a character that has been played for a long time... who alreay has a playedtime and death time set. as soon as the server tries to save the character i just logged in with that has played before. it try yo save to db a playtime of 145 and a deathtime of -9223372036854775808. both of those values are wrong at that point since the values before that should have been loaded from the db are
+------------+---------------------+
| PlayedTime | DeathTime |
+------------+---------------------+
| 141131 | 139900 |
+------------+---------------------+


so the least it should be doing is saving the same death time since i have not died yet.

[Blue]

The negative deathtime is there since the beginning of that field. Better we set it to 0 for init. I think perhaps new mysql driver makes some probs with that number?

[Nocto]

+----------------------+
| DeathTime |
+----------------------+
| -9223372036854775808 |
| -9223372036854775808 |
| -9223372036854775808 |
| [NULL] |
| -9223372036854775808 |
| [NULL] |
| -9223372036854775808 |
| [NULL] |
| -9223372036854775808 |
| 115763 |
| -9223372036854775808 |
| [NULL] |
| 98513 |
| 57271 |
| 75497 |
+----------------------+

here an example of the deathtimes in our db... Thrydon can it be that you (camelotserver, right?) run a xml database ?

it maybe the new sql driver, yes... because after that these errors came up. normally that value should fit into an bigint(20) but it doesn't in the new sql driver.

[bstag]

I believe it also has issues reading the values from the db.. which set my played time and deathtimes wrong. And since i have daid with this character before but not when i have loaded up on new version is should just be spiting out the same values witht he increases in play time. i looks to reset both to the negative number. which i do see as said in my db before for other chars. just not the one i loged in with.

[nor]

Don't think that number makes problems anywhere else and it points on problems with DB - it should be able to store min and max values. DB code needs a fix if it really is the problem now especially if it even reads wrong values.

[bstag]

i will just put old fraking sql handler back in... and prove it...



tho i should not have to. the basics of debuging what freaking changed... let me tell you it was not my db.

[nor]

That is not what I said; what I wanted to say is long.MinValue was making no problems before and should not.