PDA

View Full Version : D2010, EL 6.0.22 and Indy 10


braindead0
31-Dec-2009, 08:16 PM
It appears that EIdSocketError 10054 (and other) errors in Indy threads with EL configured to restart the application after 1 errors in 1 minutes, caused EL to terminate the application.

As soon as I turned off that 'Behaviour' option my application continued fine.

I haven't tried duplicating in a small application, however it should be easy to setup an Indy HTTPServer, then in the OnGet event query some data or some other operation that takes a little time. I found that I could get a socket exception 10054 by refreshing the page and quickly closing the browser/browser tab (killing the socket of course).

I tried tracking this down in EL, however once I found a workaround I gave up on that.

I also found that filtering doesn't appear to be working correctly for EIdSocketError (maybe others). I had EIdSocketError in the exception filters list, with handler set to EurekaLog, Dialog and Action both set to None (and exception filter 'Activate' checked of course). When I get this error EL is still sending a report. I changed the filter to handler (none) and that fixed the problem. I can also set the filter to RTL and no problem (probably expected).

Alex
07-Jan-2010, 12:30 PM
Hi,

Sorry for the late reply.

It appears that EIdSocketError 10054 (and other) errors in Indy threads with EL configured to restart the application after 1 errors in 1 minutes, caused EL to terminate the application.
If EIdSocketError occurs too often - this will surely trigger the restart/terminate rule, so it's not surprising, right? ;)
You may want to disable this behaviour - go to "Advanced Options" page and select "none" in behaviour options.

I also found that filtering doesn't appear to be working correctly for EIdSocketError (maybe others).
You may forgot to set exception type (handled/unhandled/both). Otherwise it may be a bug in EurekaLog.

Dialog and Action both set to None
Dialog and Action options controls dialog and action. They do not control sending or "Terminate/Restart application after N errors in M minutes".

When I get this error EL is still sending a report.
I think that this is expected. There are no options in filter for sending.

Sorry, but I don't quite get what you want us to do :(
Please, see this article: http://blog.eurekalog.com/tips-tricks-part-1/ may be it will help.

braindead0
22-Jan-2010, 06:04 PM
Hi,

Sorry for the late reply.


If EIdSocketError occurs too often - this will surely trigger the restart/terminate rule, so it's not surprising, right? ;)
The point is that ONE single EIdSocketError causes the application to terminate.

Alex
25-Jan-2010, 08:19 AM
Hi,

Can you send us a demo to illustrate this issue?