[
https://issues.apache.org/jira/browse/UIMA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826668#comment-13826668
]
Marshall Schor commented on UIMA-3437:
--------------------------------------
ok, that wasn't it... :-) The problem is that the spots that set the recovery
interval to 0 set it in a path *after* the call happened that broke the
connection. The fix was to add a set-to-0 in the JmsInputChannel stop method,
before the "stopChannel" call.
> make the uima-as extended tests go faster
> -----------------------------------------
>
> Key: UIMA-3437
> URL: https://issues.apache.org/jira/browse/UIMA-3437
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.4.2AS
> Reporter: Marshall Schor
> Assignee: Jerry Cwiklik
> Priority: Minor
>
> The extended tests spend a lot of time waiting for timeouts. Find these and
> reduce the timeouts where feasible to make the tests run faster. An example:
> When a service is "undeployed", that process tweaks some code path where the
> Spring JMS code detects a failed communication (in the listener, I think),
> and goes into a retry. This shouldn't be happening.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
