[ https://issues.apache.org/jira/browse/UIMA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738992#action_12738992 ]
Jerry Cwiklik commented on UIMA-1454: ------------------------------------- Fixed the code to silence connection failure exceptions. Instead of a stack trace a message is logged indicating a connection problem. Also added a DoNotProcess list and a dedicated cleanup thread that removes entries from the list after 30 minutes. > Stale requests are processed and subsequently labeled as exceptions > ------------------------------------------------------------------- > > Key: UIMA-1454 > URL: https://issues.apache.org/jira/browse/UIMA-1454 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Reporter: Eddie Epstein > > 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 {identified reply queue name} > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.