hantsowl
Member of DD Central
Posts: 672
Likes: 546
|
Post by hantsowl on May 4, 2018 9:39:12 GMT
logged out, logged in again, went straight through The logout may not be the reason. Reading updates above the transactions are finally going ahead so it is more likely the timing rather than the logout. There was a similar delay on loan 101 and it took almost 30 minutes of refreshes to buy there also. You can test the logout theory when the next small loan is launched. Try the logout after a couple of failures and see if it works then.
|
|
boundah
Member of DD Central
Posts: 367
Likes: 430
|
Post by boundah on May 4, 2018 9:44:03 GMT
OK, first attempt at 10.00am followed by 17 attempts over 30 mins. Longest wait during processing 2m45", average 1m35". A variety of error messages including 'Error in running SQL Query', 'Error in running Scalar SQL Command', 'The target loan has been updated in the system. Please refresh and try again', 'This Loan instance in memory is out-of-date' & 'Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction'. Eventual success after 35 mins, which was a relief as the loan was filling quickly. Note to self: if the transaction doesn't go through within c10s it's probably stuck. It may be best to cancel and try again rather than sit staring at a 'processing' notice. ablrate - you really need to get this sorted pronto. A lot of your hard-earned goodwill is at risk if you can't get the basics right.
|
|
garfield
Member of DD Central
Posts: 490
Likes: 268
|
Post by garfield on May 4, 2018 9:44:34 GMT
Then another FINAL excuse; Unexpected error occurred: Transaction (Process ID 111) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.NEXT try, got the money on SUCCESSFULLY. WELCOME to the Computer Game called Ablrate Available Loans Day. Designed to frustrate, but you deserve a cup of tea afterwards, when successful... You mean you didn't get Process IDs 84, 90 and 99? Perhaps we can do some swaps to get a full set? I got my money in on the 12th attempt. PHEW!!!
|
|
|
Post by dan1 on May 4, 2018 9:46:12 GMT
Ha! A fourth error! Reset Focus Failed: The target loan has been updated in the system. Please refresh and try again. Ref: 36ea3727-8754-4f4a-8e91-f901a64589d8. Tried to withdraw the cash as got bored. Failed. C'mon! Oh, the cash has disappeared anyway. FWIW this is simply the loan identifier used in the system
|
|
ding
Member of DD Central
Posts: 238
Likes: 132
|
Post by ding on May 4, 2018 9:51:50 GMT
All. Please carry in being inpatient and carry on refreshing / clashing. Still waiting for bank feed handle to be wound. Pain in the ass typing in all your details into the debit card form.
|
|
|
Post by supernumerary on May 4, 2018 9:52:38 GMT
OK, first attempt at 10.00am followed by 17 attempts over 30 mins. Longest wait during processing 2m45", average 1m35". A variety of error messages including 'Error in running SQL Query', 'Error in running Scalar SQL Command', 'The target loan has been updated in the system. Please refresh and try again', 'This Loan instance in memory is out-of-date' & 'Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction'. Eventual success after 35 mins, which was a relief as the loan was filling quickly. Note to self: if the transaction doesn't go through within c10s it's probably stuck. It may be best to cancel and try again rather than sit staring at a 'processing' notice. ablrate - you really need to get this sorted pronto. A lot of your hard-earned goodwill is at risk if you can't get the basics right. Cor!!!! 'Error in running Scalar SQL Command'Even I didn't get 'Scalar SQL Command' contacting me... That must mean something very important!
|
|
|
Post by dan1 on May 4, 2018 9:54:00 GMT
I do have sympathy with ablrate on this one. It sounds as if the developers implemented a change to prevent concurrent bids, which must be a right PITA to sort out if there are simultaneous transactions on either the primary or secondary markets. Obviously, an unintended consequence of this is repeated failed transactions. The system has issues but at least it's in development and enhancements are added regularly (Trading Reports, for example) however frustrating it is.
|
|
|
Post by supernumerary on May 4, 2018 9:59:48 GMT
Then another FINAL excuse; Unexpected error occurred: Transaction (Process ID 111) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.NEXT try, got the money on SUCCESSFULLY. WELCOME to the Computer Game called Ablrate Available Loans Day. Designed to frustrate, but you deserve a cup of tea afterwards, when successful... You mean you didn't get Process IDs 84, 90 and 99? Perhaps we can do some swaps to get a full set? I got my money in on the 12th attempt. PHEW!!! I don't mind doing some 'swaps', BUT I haven't got the ALL important ; 'Error in running Scalar SQL Command'WE will all have to ask boundah nicely for that one...
|
|
|
Post by ablrate on May 4, 2018 10:02:13 GMT
We are aware of the errors on the site. The developers are working on it and we have changed some of the architecture to stop concurrent trades etc. Clearly what they have done has not worked so they are back to the drawing board and are working on it now. These changes have been created to solve some complex trading on the platform. As an idea we archived a few months worth of audit logs and there were 3 million records... so as the platform grows we have to make sure that the architecture is improving. Unfortunately, on occassion, something breaks, it is the nature of the beast.
That is what has happened here and we are very sorry for the incovenience.
|
|
|
Post by dan1 on May 4, 2018 11:03:11 GMT
Thanks for email ablrate regarding concurrent transactions. Great communication and will be appreciated most by those who don't visit forums.
|
|
marka
Member of DD Central
Posts: 224
Likes: 175
|
Post by marka on May 4, 2018 14:03:54 GMT
... which must be a right PITA to sort out if there are simultaneous transactions on either the primary or secondary markets. Not really. Its software engineering 101.
|
|
|
Post by dan1 on May 4, 2018 14:10:04 GMT
... which must be a right PITA to sort out if there are simultaneous transactions on either the primary or secondary markets. Not really. Its software engineering 101. By "PITA" I was referring to the situation resulting from the concurrent trades not the cause. For example, £100 available on SM attracts 2 simultaneous purchases - what do you do as a platform? £50 to each purchaser, £100 & £0,... point is someone is going to be unhappy. As for software engineering, well, probably best to keep my thoughts to myself but I'm guessing in 50 years time people will look back to now and think how on earth did they put up with stuff like the recent TSB debacle.
|
|
nw99
Posts: 340
Likes: 114
|
Post by nw99 on May 4, 2018 14:45:54 GMT
We are aware of the errors on the site. The developers are working on it and we have changed some of the architecture to stop concurrent trades etc. Clearly what they have done has not worked so they are back to the drawing board and are working on it now. These changes have been created to solve some complex trading on the platform. As an idea we archived a few months worth of audit logs and there were 3 million records... so as the platform grows we have to make sure that the architecture is improving. Unfortunately, on occassion, something breaks, it is the nature of the beast. That is what has happened here and we are very sorry for the incovenience. Excellent communications
|
|
andy1
Member of DD Central
Posts: 103
Likes: 107
|
Post by andy1 on May 4, 2018 15:48:21 GMT
By "PITA" I was referring to the situation resulting from the concurrent trades not the cause. For example, £100 available on SM attracts 2 simultaneous purchases - what do you do as a platform? £50 to each purchaser, £100 & £0,... point is someone is going to be unhappy. I vote gypsy knife fight.
|
|
boundah
Member of DD Central
Posts: 367
Likes: 430
|
Post by boundah on May 4, 2018 16:33:35 GMT
You mean you didn't get Process IDs 84, 90 and 99? Perhaps we can do some swaps to get a full set? I got my money in on the 12th attempt. PHEW!!! I don't mind doing some 'swaps', BUT I haven't got the ALL important ; 'Error in running Scalar SQL Command'WE will all have to ask boundah nicely for that one... A Scalar is only issued to ABL's most persistent customers. I'll put mine up on the secondary market soon at 120% min.
|
|