[IGNITE-12316] Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Dmitriy Govorukhin
• Created: 22/Oct/19 07:40
• Updated: 06/Nov/19 12:28
• Resolved: 06/Nov/19 08:42

Description

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

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}

1. Start cluster, start active transaction in thread
2. Assert that in Forbidden operation inside transaction scenarios exception occurs with log information about cache name and reason
3. Finish running transaction, assert that there is no exception while evaluating Forbidden operation inside transaction

 

Issue Links

• is related to: IGNITE-10761 GridCacheProcessor should add info about cache in excecption message, if applicable.
• links to: GitHub Pull Request #6995