Opened 8 years ago
Closed 4 months ago
#4362 closed enhancement (fixed)
ecmtimeoutlimit is needed
Reported by: | AbrahaM | Owned by: | |
---|---|---|---|
Priority: | minor | Component: | Reader |
Severity: | medium | Keywords: | ecmtimeoutlimit proxy reader stability improvement |
Cc: | Sensitive: | no |
Description
Reason for enhancement
I'm quite often getting reports from friends (or observing it myself) where proxy (or reader) is hung in state in which returned result is not "not found" but "timeout".
We have possibility to reset reader/proxy that is giving "not found" result by usage of ecmnotfoundlimit which will reset proxy/reader after reaching limit of "not foudns".
but we don't have possibility to reset reader/proxy that is giving "timeout", and proposed ecmtimeoutlimit would fill that gap in funtionality.
Possible impacts on other features
None
Change History (3)
comment:1 by , 8 years ago
Summary: | ecmtimeoutimit is needed → ecmtimeoutlimit is needed |
---|
comment:3 by , 4 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I reproduced your case using proxy readers. Obviously you're absolutely right.
If I simulated NOK's, then <ecmnotfoundlimit> option does the job perfectly, if I simulate timeouts, then indeed it hangs and there's no way to reset reader/proxy in automatic way.