No, initial EntryProcessorException is lost. Instead, root cause of this exception is thrown. This is a bug somewhere inside our "convert" methods for exceptions.
On Wed, Jul 8, 2015 at 7:05 PM, Yakov Zhdanov <[email protected]> wrote: > I would like someone picks it up and get to the bottom of this. I suspect > original exception may be in the cause of the one thrown outside. > > -- > Yakov Zhdanov, Director R&D > *GridGain Systems* > www.gridgain.com > > 2015-07-06 18:05 GMT+03:00 Vladimir Ozerov <[email protected]>: > > > Igniters, > > > > I noticed that IgniteFuture.chain() could loose exceptions. I created the > > ticket https://issues.apache.org/jira/browse/IGNITE-1097 with example of > > lost EntryProcessorException. > > > > It appears that the problem is caused by some very sophisticated magic we > > do with exceptions when calling "chain()", "listen()", etc. > > > > Looks pretty annoying to me as public API is affected. Can anyone look at > > it? > > > > Vladimir. > > >
