![]() ![]() Re-trying the request itself might also work. This varies depending on what client you are using to communicate with the SLAPI, but increasing your timeout limit to several minutes may help. However there are a few things you can try. There isn’t really a hard limit on how many objects you can request in an API call, as it really just depends on how long it takes our database to get them all collected for you. Each time you make this API call, our database has to pull all of this information together before returning it to you, and eventually you’ll get hit with this error, and wonder what went wrong. Time goes by, and slowly that API call starts taking a bit longer as each month you get increasingly more complex invoices, more tickets, hardware etc. Which all works fine because your account is new and doesn’t have many of those things on it. Then you add an object mask to that API call to pull in various relational properties, like invoices, tickets, hardware etc. Lets say you want to get information about your account, so you make a API call to SoftLayer_Account::getObject, which works perfectly fine. When this error is encountered, there are three common solutions to head off the error by remedying either the timeout directly or how the API returns the results. In truth, it is a client side error provided when a timeout occurs while waiting for a response from the API. This error most commonly met when working with a large sets of data and can be a bit cryptic, as it seems to imply some sort of connection issue. Fortunately, it is not terribly difficult to avoid. "Error Fetching http headers" is a common error to encounter when working with the SLAPI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |