Devis, I think this happens because of thread starvation. Both compute job and service proxy invocations are processed in the same thread pool, so if you synchronously call a service from a job, you can run out of threads and get stuck. Can you replace the service with another callable? In this case you can execute asynchronously and use continuations [1] to avoid starvation.
[1] https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Timeout-was-reached-before-computation-completed-tp10712p10844.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
