Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When a client submits one or more requests to a service and then terminates
before the service has a chance to reply, the service will still process the requests
and then fail trying to send the reply with a long stack trace.
There are two problems here: processing a request which cannot be replied to,
and throwing an exception for expected behavior.
The following is suggested:
1. catch these exceptions and log a single line at INFO level that a reply could
not be sent to
2. put this reply queue on a "do not process" list to be checked before processing
new requests.
3. clean up the "do not process" list based on time or max number of entries.