[
https://issues.apache.org/jira/browse/UIMA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein closed UIMA-1097.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2C)
Turns out the TimeToLive situation with AMQ 4.1.1 is more complicated. Messages
that have expired according to the AMQ definition also fail to be delivered to
Java consumers when using Java 6 (or at least sun java 1.6_02 on Linux). Given
the fact that TimeToLive problems are also on Java, there is no point in
disabling the C++ consumer. This issue is closed and a new issue opened on UIMA
AS describing the situation more fully.
> C++ service wrapper is losing messages that have timeout values set
> -------------------------------------------------------------------
>
> Key: UIMA-1097
> URL: https://issues.apache.org/jira/browse/UIMA-1097
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
>
> UIMA-AS clients set JMS timeToLive on commands with non-zero timeout values.
> This enables the JMS system to automatically clean up commands that have
> timed out waiting for a service to receive and process them.
> The ActiveMQ C++ client appears to be computing expiration incorrectly, based
> on the local consumer clock. Commands to C++ services using the native C++
> service wrapper may be lost unless the producer and consumer clocks are
> exactly in synch.
> The problem can be easily fixed by disabling expiration for the C++ client.
> Note that for AMQ v4.1.1 currently used with UIMA-AS, expiration is not
> enabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
