[
https://issues.apache.org/jira/browse/UIMA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826650#comment-13826650
]
Marshall Schor commented on UIMA-3437:
--------------------------------------
Code inspection shows that the recovery interval is being set to 0. However,
it's not under synchronized, and it's not marked volatile. So, it's probably
not being "effective" even when set to 0 because of the Java memory model, and
the fact that the listener is running in another thread. There's some evidence
for this, because if / when I single step some of this code, the 30 second
timeout doesn't seem to happen...
> 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)
