[
https://issues.apache.org/jira/browse/JENA-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985123#comment-14985123
]
ASF subversion and git services commented on JENA-1060:
-------------------------------------------------------
Commit 0df098ba0c24581c49ab187950f3c5bfcdf1b6a0 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=0df098b ]
JENA-1060: Use "Alarm" instances.
> AlarmClock can not cancel alarms properly.
> ------------------------------------------
>
> Key: JENA-1060
> URL: https://issues.apache.org/jira/browse/JENA-1060
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.0.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> The {{AlarmClock}} code does not cancel alarms properly (it hides and drops
> the {{ScheduledFuture}} needed to cancel an alarm).
> The query timeout code is not exposed to this issue because it has to be
> defensive about a timeout going off unexpectedly anyway (it can't yield the
> first result and reset timeout1 to timeout2 as a single compound, atomic
> action). Similarly, timeouts going off on finished queries have to be
> tolerated.
> The net effect on ARQ is a small build up of outstanding alarms which will
> eventually go away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
