General Betting
Welcome to Live View – Take the tour to learn more
Start Tour
There is currently 1 person viewing this thread.
It's firing off exceptions like machine gun bullets.
Why don't BF clear out the tech staff and start again? What's to lose?
Why don't BF clear out the tech staff and start again? What's to lose?
Show More
First time in a long time an upgrade has caused a problem with the API.
which markets ... it looks ok to me, but i've only just fired up my app
don't want to go out and leave it running if there are serious probs.
don't want to go out and leave it running if there are serious probs.
getting BET_IN_PROGRESS in the horse markets, but it's not a market-specific prob.
You're brave if you set it going and then go out!
You're brave if you set it going and then go out!
no, i'm not brave, that's why i asked .... have to take the lappie out with me and rely on the alleged 'cloud' :)
Weird - every now and then everything flashes blank - all the bets and lays - then reappears.
Yes have the same problem zooot. Will be interesting to see the effect of this upgrade when the racing starts.
I had some huge lags before the upgrade this morning and a couple since. May have been something other than BF. But this flashing since the upgrade is very annoying and unsettling - makes you wonder if it could go pear shaped at a critical time.
Said they were hoping to have it fixed within 20 minutes just after 11:00. Still problems though
It's BET_IN_PROGRESS, which is a database timeout.
Still happening, but less frequently than it was.
Still happening, but less frequently than it was.
I'm still getting a load of general API_ERRORs. Apparently, it is still being investigated.
got worse again now. I'm packing it in for the day.
Yep, still getting errors on PlaceBets and CancelBets calls. Not so many on Read calls now though.
they've only just bothered to put it up on the service forum!
Any ETA on when it will be fixed (or rolled back) ?
according to service API issues have been resolves but the site as a whole is fecked :)
API definitely still in trouble. Getting all kinds of wonderful error messages now.
I'm knocking off for the day thought it was running ok but now getting error messages and frozen screen on desk top and laptop, not worth the risk
API seems t have taken a definite dislike for Fairyhouse ... had freezeups on every race there (socket errors)
Still having problems with Loading Markets using the API.
Just got the error: There is an error in XML document (2, 812).
Just got the error: There is an error in XML document (2, 812).
The idea of these upgrades is to deinstall a computer or two each time.
If the users get used to the degraded service, they sell them on eBay.
This also helps to reduce the electricity bill.
hth.
If the users get used to the degraded service, they sell them on eBay.
This also helps to reduce the electricity bill.
hth.
What does QA stand for again?
Quite Awful, of course.
Quite Awful, of course.
People can't get a bet on for the 60 million enquiries a second fired in by the ferengi.
I doubt that HFT practices are the problem.
a) it was working yesterday.
b) the enquiries are a different system load than the bet processing, and are likely to be cached. They are charged differently under the newish penalising scheme.
c) the system has never been fast enough for people to benefit from HFT anyway.
a) it was working yesterday.
b) the enquiries are a different system load than the bet processing, and are likely to be cached. They are charged differently under the newish penalising scheme.
c) the system has never been fast enough for people to benefit from HFT anyway.
http://www.theregister.co.uk/2009/12/10/linx_failure/
I doubt that HFT practices are the problem
I agree but if they didn't need feeding the system would only have a minute fraction of the complexity which would make it a lot more stable.
I agree but if they didn't need feeding the system would only have a minute fraction of the complexity which would make it a lot more stable.
That's odd. I was just about to reply to a post re LINX failure when it disappeared.
I think it was a red herring anyway. I delved a bit further into the site he referred to and found:
The problem began at 18.35 last night and lasted for about an hour.
I think it was a red herring anyway. I delved a bit further into the site he referred to and found:
The problem began at 18.35 last night and lasted for about an hour.
According to twitter lots of users still experiencing issues due to LINX problems
If LINX is having any effect then it means BF have been outsourcing their server farms.
Just ran the Kemp 17:00 using the API and it worked without any errors.
Thing are looking up.
Thing are looking up.
Hopefully next Mondays update is a little smoother....
it seems find to me today ... reminds me of my time helpdesking:
"Have you tried switching it off an on again?"
"Yes of course"
"Ah well, give it a couple of minutes to settle in."
"Have you tried switching it off an on again?"
"Yes of course"
"Ah well, give it a couple of minutes to settle in."
OK today.
Why do they call these ordeals "upgrade?"
Why do they call these ordeals "upgrade?"
hmmmm... the soccer/football markets seems to have disappeared completely from my getAllMarkets call today
was working fine yesterday
was working fine yesterday
hmmmm they've appeared now after 3rd login
how strange
how strange
Post Your Reply
Please login to post a reply.
Wonder
Instance ID: 13539