[
https://issues.apache.org/jira/browse/UIMA-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906065#comment-13906065
]
Lou DeGenaro edited comment on UIMA-3577 at 5/16/14 5:10 PM:
-------------------------------------------------------------
See Jira 3828.
was (Author: lou.degenaro):
Once that all JPs have stopped, perhaps JD should insure queue is purged.
// The ActiveMQ JMX domain
> String amqDomain = "org.apache.activemq";
>
> // The parameters for an ObjectName
> Hashtable<String, String> params = new Hashtable<String, String>();
> params.put("Type", "Queue");
> params.put("BrokerName", brokerName);
> params.put("Destination", queueName);
>
> // Create an ObjectName
> ObjectName queueObjectName = ObjectName.getInstance(amqDomain, params);
>
> // Create a proxy to the QueueViewMBean
> QueueViewMBean queueProxy = (QueueViewMBean)
> broker.getManagementContext().newProxyInstance(queueObjectName,
> QueueViewMBean.class, true);
>
> // Purge the queue
> queueProxy.purge();
>
> DUCC job driver (JD) should auto-retry lost work items
> ------------------------------------------------------
>
> Key: UIMA-3577
> URL: https://issues.apache.org/jira/browse/UIMA-3577
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Environment: Currently work item is "lost" after 5 minutes and
> callback #2 has not triggered.
> Lost work items are presently not auto-retried.
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 1.1.0-Ducc
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
