AMR keep crashing?
- Thread starter perocJ
- Start date
Sniper
Regular Member
- Dec 30, 2008
- 472
- 218
It's DBC (DeathByCaptcha). Their API URL (This one: http://api.dbcapi.me/api) intermittently times out and the dll that they require software vendors to use doesn't properly handle the timeout situation. Unfortunately, the blow up in the dll can't be handled in AMR using a traditional Try/Catch/Exception which is already programmed into AMR, so the folks over at DBC need to add this into their DLL in order to properly handle this crash situation and at least return a server timeout string rather than just let the dll blow up.
Sniper
Regular Member
- Dec 30, 2008
- 472
- 218
Direct from DBC Support:
A small group of users might be experiencing issues with the service due to some connectivity inconveniences we're facing with our DNS provider. We're expecting a resolution for this situation in a short period of time (the DNS needs to be fully propagated).
I sincerely apologize for all the inconveniences that this may be causing you and your customers. Please note that there's no need to take further actions on this.
A small group of users might be experiencing issues with the service due to some connectivity inconveniences we're facing with our DNS provider. We're expecting a resolution for this situation in a short period of time (the DNS needs to be fully propagated).
I sincerely apologize for all the inconveniences that this may be causing you and your customers. Please note that there's no need to take further actions on this.
- Dec 21, 2009
- 808
- 170
Hi,
Thanks for sharing the information. We're expecting to have this ready ASAP.
Best Regards,
Sniper
Regular Member
- Dec 30, 2008
- 472
- 218
Hi James - I mentioned this in another thread, but it seems more appropriate here:
Regarding your dll that interacts with the api URL that is timing out - Could you PLEASE make your dll crash proof so it doesn't blow up when the API URL times out? There is no way to handle this crash situation outside of the dll, and when your dll blows up, it blows up AMR as well. Also, can you ensure that if the users internet connection drops, even for a second, that any httpwebrequests don't result in a crash. I moved AMR away from the HTTP api because you asked me to, and I have a feeling that a lot of the ghost crashes in the past are completely related to unhandled exceptions in your dll.
Regarding your dll that interacts with the api URL that is timing out - Could you PLEASE make your dll crash proof so it doesn't blow up when the API URL times out? There is no way to handle this crash situation outside of the dll, and when your dll blows up, it blows up AMR as well. Also, can you ensure that if the users internet connection drops, even for a second, that any httpwebrequests don't result in a crash. I moved AMR away from the HTTP api because you asked me to, and I have a feeling that a lot of the ghost crashes in the past are completely related to unhandled exceptions in your dll.
- Dec 21, 2009
- 808
- 170
Hi there!,
You could check the source code provided on our APIs (http://www.deathbycaptcha.com/user/api) to work this out in the meantime. However, I'll be sending you a fixed .dll soon.
Best Regards,
- Dec 21, 2009
- 808
- 170
Hi Guys,
Just for your information, I recommend everyone who wants to follow up on Death By Captcha recent, past issues to take a look at this thread --> http://www.blackhatworld.com/blackh...-about-recent-major-upgrade-other-topics.html
Best Regards,
Just for your information, I recommend everyone who wants to follow up on Death By Captcha recent, past issues to take a look at this thread --> http://www.blackhatworld.com/blackh...-about-recent-major-upgrade-other-topics.html
Best Regards,
Sniper
Regular Member
- Dec 30, 2008
- 472
- 218
From what I can tell, DBC servers are back to running as normal and if/when a timeout on their API server happens, they produce a usable message rather than a "server is taking too long to respond" error. Because of this, the DBC DLL that AMR uses doesn't blow up any more. Also, the emails stopped coming in, so I think most people are back in a happy place right now.