Daniel, A couple of things: - according to javadocs, IgniteMessaging.send() returns void. To obtain the future you should instead call IgniteMessaging.future() immediately following the send() call.
- in some cases, Ignite's 'async' operations are actually synchronous. Ignite's interpretation of 'asynchronous' is quite unorthodox and the users should be aware of possible deadlocks and thread starvation, among other things. Regards, Andrey _____________________________ From: Daniel Stieglitz <[email protected]<mailto:[email protected]>> Sent: Saturday, November 5, 2016 1:47 PM Subject: Async messaging To: <[email protected]<mailto:[email protected]>> Hi folks: We are trying to get messaging working asynchronously. Take a look at the code below: IgniteMessaging rmtMsg = grid.message().withAsync(); def future = rmtMsg.send(destination, message); log.debug("got future ${future}"); That code runs synchronously and the debug says "got future null" Is there something else we need to configure to get this working? Dan
