Hi Yakov, Thanks for the prompt reply, I'll get the info together into the Jira ticket for you as soon as I can.
I use Apache Ignite in the following way: - I create an IgniteCallable<MyResultObject> object with a unique ID. - The XML/XSL file assets are added to the "ASSETS" cache (cache stored on the nodes). - Create an IgniteCompute object (pulling from available remotes with Async). - Affinity call with the UUID, IgniteCallable(above) and "ASSET" cache key. - Create a future from IgniteCompute - Attach IgniteInClosure<IgniteFuture<MyResult>> to the the future. The server has it's own queue system to limit the number of jobs submitted to Apache Ignite and releases more when the futures come back to release them. I guess this would cause starvation? but I have no idea what this would mean to my application and/or if it's a bad thing? Thanks again, Darren. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Futures-not-being-triggered-tp773p775.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
