You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2019/10/22 07:41:00 UTC
[jira] [Created] (IGNITE-12316) Extend test coverage [IGNITE-10761]
GridCacheProcessor should add info about cache in exception message, if
applicable.
Kirill Tkalenko created IGNITE-12316:
----------------------------------------
Summary: Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.
Key: IGNITE-12316
URL: https://issues.apache.org/jira/browse/IGNITE-12316
Project: Ignite
Issue Type: Improvement
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
Fix For: 2.8
Test cache operations that should fail inside tx thread
||*Forbidden operation inside transaction*||
|dynamic single cache start|
|dynamic start of multiple caches|
|dynamic cache destroy|
|dynamic destroy of multiple caches|
|dynamic cache close|
|reset cache state|
{quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
# Start cluster, start active transaction in thread
# Assert that in *Forbidden operation inside transaction* scenarios exception occurs with log information about cache name and reason
# Finish running transaction, assert that there is no exception while evaluating *Forbidden operation inside transaction*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)