[
https://issues.jboss.org/browse/ISPN-2485?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-2485:
-------------------------------------------
Anna, this is a somewhat different timeout than the one in Future#get(long,TimeUnit). This
timeout was created to enable tasks to be run longer than default sync replication timeout
which was timeout before. Clients would use this timeout to allow tasks to run beyond
sync.repl timeout (default 15 sec). But now that you mention this, the confusion is
obvious. Thinking how to resolve this..... any suggestions?
DefaultExecutorService.DistributedTaskBuilder timeout(long to,
TimeUnit u) doesn't use the passed to timeout
------------------------------------------------------------------------------------------------------------
Key: ISPN-2485
URL:
https://issues.jboss.org/browse/ISPN-2485
Project: Infinispan
Issue Type: Bug
Components: Distributed Execution and Map/Reduce
Reporter: Anna Manukyan
Assignee: Vladimir Blagojevic
Hi,
the issue is the following:
1. DistributedTaskBuilder is created with callable which sleeps for 10 seconds.
2. The timeout is set to DistributedTaskBuilder for 10 milliseconds.
3. Then the built DistributedTask is executed with DefaultExecutorService on the
different node rather than the executorservice was attached to.
4. In 10 milliseconds, the TimeoutException should be thrown, but it doesn't.
The thing is, that although timeout is passed to timeout(long timeout, TimeUnit unit)
method of DefaultExecutorService.DistributedTaskBuilder class, but the method parses and
sets not the passed value, but the one which was given to task builder during
initialization.
Please find the reproducing test here:
https://github.com/andyuk1986/infinispan/blob/DIST_EXEC_TESTS/core/src/te...
Please find the proposed fix here:
https://github.com/andyuk1986/infinispan/blob/DIST_EXEC_TESTS/core/src/ma...
(line 734)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira