Getting 404 errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pillbox
    Junior Member
    • Oct 2014
    • 7

    #16
    Very rarely i am seeing missing information from the australian exchange with no reported error. For example (called at approximately 2014-11-11 10:57:08 GMT):

    request:
    {"jsonrpc":"2.0","method":"SportsAPING/v1.0/listEventTypes","id":"1","params":{"filter":{}, "locale":"en_GB"}}

    response:
    {"jsonrpc":"2.0","result":[],"id":"1"}

    This should be an error. There clearly are event types and the operation succeeds before and after.

    Comment

    • ~Drive Blind
      Junior Member
      • Mar 2009
      • 9

      #17
      Still happening

      The 404 errors and TIMEOUT_ERROR problems are still happening every day on the Australian endpoint.

      Today 4.59am until 5.03am I had lots of TIMEOUT_ERROR, this leaves positions exposed and means I am unable to close a market out.

      Lots of people are having this problem but no resolution yet ?

      Comment

      • Fred77
        Junior Member
        • Jan 2009
        • 37

        #18
        Code:
        03:23:03 3rdDec listMarketBook (11.95 seconds) Response:{"jsonrpc":"2.0","error":{"code":-32099,"message":"ANGX-0006","data":{"exceptionname":"APINGException","APINGException":{"errorDetails":"","errorCode":"UNEXPECTED_ERROR","requestUUID":"prdang003-12022349-000017c2d4"}}},"id":1}
        
        03:23:24 3rdDec listMarketBook (20.12 seconds) timed out
        
        03:23:46 3rdDec listMarketBook (20.14 seconds) timed out
        
        03:23:50 3rdDec keepAlive (1.70 seconds) ok
        
        03:23:54 3rdDec listMarketBook (1.69 seconds) receive error
        
        03:24:02 3rdDec listMarketBook (0.14 seconds) HTTP_CODE:404
        
        03:24:18 3rdDec getAccountFunds (1.146 seconds) ok
        
        03:24:19 3rdDec listMarketBook (0.12 seconds) HTTP_CODE:404 
        
        03:24:20 3rdDec listMarketBook (0.12 seconds) HTTP_CODE:404
        
        03:24:22 3rdDec listMarketBook (0.12 seconds) HTTP_CODE:404
        
        03:24:26 3rdDec listMarketBook (0.12 seconds) HTTP_CODE:404
        
        03:24:35 3rdDec listMarketBook (0.12 seconds) HTTP_CODE:404
        
        03:25:02 3rdDec listMarketBook (11.85 seconds) receive error
        
        03:25:38 3rdDec listMarketBook (3.96 seconds) receive error

        Comment

        • HelloMyBets
          Junior Member
          • Dec 2014
          • 1

          #19
          It is still happenning Now

          The 404 error show on my every request

          Comment

          • BetfairDeveloperProgram
            Administrator
            • Oct 2008
            • 679

            #20
            Hi All,

            We have made a further release today which we expect to reduce the number of 404 incidences on the AUS Exchange and improve AUS Exchange performance overall.

            Kind Regards

            Neil

            Comment

            • Mr Magoo
              Junior Member
              • Jan 2011
              • 86

              #21
              Well I haven't seen any 404 errors today, for a change. However, I have pages and pages of TIMEOUT_ERRORs, all from the Australian exchange, spread out over many hours.

              The new API is still appallingly unreliable for AUS...

              Comment

              • BetfairDeveloperProgram
                Administrator
                • Oct 2008
                • 679

                #22
                Hi Mr Magoo,

                Thanks for your feedback. We'll be making further updates next week (~ 10th December) which hopefully should improve things.

                Neil

                Comment

                • Olliep1
                  Junior Member
                  • Dec 2014
                  • 1

                  #23
                  Updates

                  Hi Neil,

                  What is the best way for us to find out when further updates have been made?

                  Cheers

                  Ollie

                  Comment

                  • BetfairDeveloperProgram
                    Administrator
                    • Oct 2008
                    • 679

                    #24
                    Hi Ollie,

                    There should now be a considerable reduction in the number of 404 issues that customers are experiencing when interacting with the AUS Exchange.

                    However, we are aware of other issue's (relating to Timeouts) which we are currently investigating and looking to resolve as part of a release next week. I should be in a position to confirm the release date tomorrow.

                    Please accept our apologies for the delay and inconvenience caused by this problem.

                    Neil

                    Comment

                    • ~Drive Blind
                      Junior Member
                      • Mar 2009
                      • 9

                      #25
                      More 404's again

                      Lots more 404's again today

                      2014-12-12 06:35:52,826 [Main Thread] ERROR GeneralLog - Internal Error
                      System.Net.WebException: The remote server returned an error: (404) Not Found.
                      at System.Net.HttpWebRequest.GetResponse()
                      at .....

                      This occurred from 06:35 constantly until 07:12.

                      Comment

                      • Mr Magoo
                        Junior Member
                        • Jan 2011
                        • 86

                        #26
                        No 404s from the AUS servers today, just one UNEXPECTED_ERROR (ANGX-0006) and four 'Server closed connection without sending any data back' errors. The connectivity isn't perfect but it's definitely improving.

                        Comment

                        • BetfairDeveloperProgram
                          Administrator
                          • Oct 2008
                          • 679

                          #27
                          Hi All,

                          Just a quick update regarding these issues.

                          The root caused has been traced to a network communication failure between services in AUS and those in hosted in the UK.

                          Our Australian networks works team are investigating potential remedial action and a timeline for this. We'll provide further information as soon as we have it.

                          Thanks for your patience in the meantime.

                          Neil

                          Comment

                          • Mr Magoo
                            Junior Member
                            • Jan 2011
                            • 86

                            #28
                            Any progress on this? I'm still seeing loads of timeouts with the Australian endpoint.

                            Comment

                            Working...
                            X