You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Veena (Jira)" <ji...@apache.org> on 2020/02/27 23:39:00 UTC

[jira] [Commented] (IGNITE-9153) Accessing cache from transaction on client node, where it was not accessed yet throws an exception

    [ https://issues.apache.org/jira/browse/IGNITE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047057#comment-17047057 ] 

Veena commented on IGNITE-9153:
-------------------------------

HI , 

I notice this behaviour as well. Ignite.cache() in the client node is giving me the exception "Cannot start/stop cache within lock or transaction" ( Please note, I am not doing ignite.getOrCreateCache().

 

Is there a solution for this ?

> Accessing cache from transaction on client node, where it was not accessed yet throws an exception
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9153
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9153
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Evgenii Zhuravlev
>            Priority: Major
>              Labels: newbie
>         Attachments: ClientCacheTransactionsTest.java
>
>
> Exception message: Cannot start/stop cache within lock or transaction. 
> Reproducer is attached: ClientCacheTransactionsTest.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)