[12:28] [Error] Unable to post your items for sale. Items placed back into your inventory
[12:28] [Error] Unable to post your items for sale. Items placed back into your inventory
[12:29] [Error] Unable to post your items for sale. Items placed back into your inventory
[12:29] [Error] Unable to post your items for sale. Items placed back into your inventory
[12:29] [Error] Unable to post your items for sale. Items placed back into your inventory
I mean... it's time to fix it for good, don't you think?
2
Comments
A developer can feel free to correct me on this, but they should ALL be hard at work this weekend fixing the game! Because they don't need to take their children to the zoo. We need this game fixed that we spend hours and hours playing and ignoring our families. So I better see results soon or heads will roll!
ok rant done.
Something important and to most players essential is broken and needs to be fixed, hopefully as soon as possible since the Auction House, Chat and Mail (if they are indeed connected) are usually things just about every player's relies on in Neverwinter.
I have been able to post things in the AH, but usually that necessitates 4-5 failed tries before being able to post different items.
Mail can be sent in a suspended mode (do it when the system is not busy) and even if it fails, it can just return the mail to sender. Mail does not need to deliver right the way.
Chat is an append mode and it should not even need a lock and it may not even in the database. Too expensive to be a database operation. It is properly implemented as a pipe or flat file.
AH with an interactive interface needs to return within a deterministic time regardless if it is a failure or success. Otherwise, the game will appear to be like hanging.
For example, the system can handle 200 AH transaction per second and the deterministic time out is 2 seconds.
In that particular second, 500 transactions coming in at the same time.
In the first second, 200 transactions were processed without problem.
In the 2nd second, another 200 pending transactions were processed and it will appear to be no problem except the extra second wait. However, the last 100 pending transactions will get lock busy and fail.
One may say, okay, make the deterministic time out to be 3 seconds. Yes, that will solve the above situation.
Then, what if there are 700 transaction coming in at that one second? The lock busy will appear in 100 transactions of that 700 transactions.
In addition, AH transactions are not equal weight. It can be posting, buying, biding, reading/searching (unless this is done as dirty read).