[jira] [Assigned] (IGNITE-5601) WriteBehind mode hide SQLExceptions

["Roman Shtykh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shtykh reassigned IGNITE-5601:
------------------------------------

    Assignee: Roman Shtykh

> WriteBehind mode hide SQLExceptions
> -----------------------------------
>
>                 Key: IGNITE-5601
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5601
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 2.0
>         Environment: Ignite 2.0.0
> Oracle JDK 1.8.0_121
> Derby 10.13.1.1
>            Reporter: Benjamin Garaude
>            Assignee: Roman Shtykh
>             Fix For: 2.0
>
>
> If an exception, e.g. SQLException occurs during a wite-behind operation, the exception is lost and appears nowhere in the logs.
> The logs basically say:
> [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: CacheJdbcPojoStore []
> [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as current buffer size is greater than 'cacheCriticalSize' or node has been stopped before store was repaired) [key=test.WriteBehindIssue$FooKey [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT]
> If we do the same with write-through mode, it fails by throwing an exception with the SQLException as cause, deep in the trace.
> Would it be possible the write-behind operation logs the SQLException, and other exception?
> You can find a test case showing that here: https://github.com/bgaraude/IgniteTest



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)