Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Jena 3.0.0
-
None
Description
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.