Time out errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • komposter
    replied
    My last timeouts:
    26.03.2015 15:50:08
    15.03.2015 11:05:49
    15.03.2015 07:45:49

    I work with non-aus server.

    Leave a comment:


  • BigSprout
    replied
    Yes,getting the same thing.
    This is getting rather frustrating, it has been going on for far too long, makes selections & placing orders a little hit & miss on the Aus markets (ggggrrrrrrr)

    Leave a comment:


  • mattyryOne
    replied
    is anyone else still having this problem?

    its been happening for several minutes right now, (14:38 AEDT) on different markets
    here is an example of the call/response
    {
    "jsonrpc": "2.0",
    "method": "SportsAPING/v1.0/listCurrentOrders",
    "params": {
    "betIds": null,
    "marketIds": ["2.101189288"],
    "orderProjection": null,
    "placedDateRange": null,
    "dateRange": null,
    "orderBy": null,
    "sortDir": null,
    "fromRecord": null,
    "recordCount": null
    },
    "id": 1
    }{
    "jsonrpc": "2.0",
    "error": {
    "code": -32099,
    "message": "ANGX-0010",
    "data": {
    "exceptionname": "APINGException",
    "APINGException": {
    "errorDetails": "",
    "errorCode": "TIMEOUT_ERROR",
    "requestUUID": "prdang019-03140051-0007e35e42"
    }
    }
    },
    "id": 1
    }

    Leave a comment:


  • mattyryOne
    replied
    unfortunately this error has been common for many months on the AUS servers.
    However, i have noticed an increase in frequency over the past week or so, including today - so issue has not been rectified

    Leave a comment:


  • Prof Pugwash
    replied
    the errors are still happening this morning.

    Leave a comment:


  • Franklin1
    replied
    Originally posted by jptrader View Post
    Seems like the problem has not completely been rectified, I just had a couple of more of these timeouts.
    me too - no noticeable improvement today

    Leave a comment:


  • jptrader
    replied
    Seems like the problem has not completely been rectified, I just had a couple of more of these timeouts.

    Leave a comment:


  • BetfairDeveloperProgram
    replied
    Hi All,

    Following a restart of the affected servers this problem has now been rectified.

    Sorry for the disruption caused by this issue.

    Kind Regards

    Neil

    Leave a comment:


  • BetfairDeveloperProgram
    replied
    Hi All,

    This issue is currently being investigated and we'll provide an update here as soon as this has been rectified.

    Please accept our apologies for the inconvenience in the meantime.

    Thanks

    Neil

    Leave a comment:


  • lmlac
    replied
    Yes I've been getting these errors intermittently all weekend. Don't see anything in the service forum about it though.

    Leave a comment:


  • jptrader
    replied
    I haven't seen these errors before Friday, but have seen them many times since, and they still appear today. I have seen them only for listMarketCatalogue calls. Some more info:

    Http Statuscode: GatewayTimeout
    Content string:
    {"detail":{"exceptionname":"APINGException","APING Exception":{"errorDetails":"","errorCode":"TIMEOUT _ERROR", "requestUUID":"prdang-28828d-02231206-001f572c70"}},"faultcode":"Server","faultstring":" ANGX-0010"}

    Leave a comment:


  • Mr Magoo
    replied
    Yes, timeouts have been extremely common with the new APIA, I see them every day. The Australian exchange is especially bad.

    Leave a comment:


  • betdynamics
    replied
    Yes.

    Betfair had timeout issues connected with market loading/navigation on Friday and they appear to have returned again today!

    Leave a comment:


  • WellDone
    replied
    Confirm

    Leave a comment:


  • r4ge
    started a topic Time out errors

    Time out errors

    My application has been running fine for over a month but now seem to be getting constant time out errors.

    Is anyone else having issues?
Working...
X