Re: Apache Ignite - RDS Aurora Question

[vkulichenko <va...@gmail.com>]

Hi babu,

Looks like the exception trace is swallowed and it is hard to see the reason
of the error. Can you temporarily switch off write-behind (set
writeBehindEnabled property to false) and try to run your test? The database
will be updated synchronously in this case and you will be able to see the
full exception trace.

I also created a ticket for exception handling issue:
https://issues.apache.org/jira/browse/IGNITE-2358

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-RDS-Aurora-Question-tp2505p2506.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite - RDS Aurora Question

[babu prasad <ba...@gmail.com>]

Thanks for the quick response Val!
Turns out I missed the default constructor in my POJO class.
All good now.

However, when running a live setup, having the ability to troubleshoot
without turning off write behind would be great and I think the jira will
help address it.

Thanks again!


On Mon, Jan 11, 2016 at 8:35 PM, vkulichenko <va...@gmail.com>
wrote:

> Hi babu,
>
> Looks like the exception trace is swallowed and it is hard to see the
> reason
> of the error. Can you temporarily switch off write-behind (set
> writeBehindEnabled property to false) and try to run your test? The
> database
> will be updated synchronously in this case and you will be able to see the
> full exception trace.
>
> I also created a ticket for exception handling issue:
> https://issues.apache.org/jira/browse/IGNITE-2358
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-RDS-Aurora-Question-tp2505p2506.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>