You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2008/03/21 17:57:26 UTC

[jira] Reopened: (UIMA-876) UIMA service requests should expire if timeout value is set

     [ https://issues.apache.org/jira/browse/UIMA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik reopened UIMA-876:
--------------------------------

      Assignee: Jerry Cwiklik

Initial fix for message timeout was incorrect. Messages sent to queues currently dont expire. Instead of using setExpirationTime() on the jms message, use MessageProducer.setTimeToLive(). Even with this fix ActiveMQ doesnt expire messages correctly. It appears that most of the messages are moved to DLQ, but a few remain in the input queue. When a consumer is restarted, those messages are not delivered. Subsequent restart of the consumer causes the broker to deliver some of the messages immediately, and after some time later the remaing messages are delivered. 

> UIMA service requests should expire if timeout value is set
> -----------------------------------------------------------
>
>                 Key: UIMA-876
>                 URL: https://issues.apache.org/jira/browse/UIMA-876
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>            Assignee: Jerry Cwiklik
>             Fix For: 2.2.2S
>
>         Attachments: uimaj-as-activemq-UIMA-876-patch.txt, uimaj-as-jms-UIMA-876-patch.txt
>
>
> Service requests with a timeout >0 should set time-to-live for the message to the timeout value. If unprocessed after the timeout period, JMS should discard the messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.