[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-1313:
-------------------------------------------
Agreed. Right now, there is little I can to do solve this issue appropriately. Most likely
we will add a new configuration element for distributed executors where one of the
configuration settings will be a task timeout.
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL:
https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.FINAL
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira