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

Ilya Shishkov updated IGNITE-20799:
-----------------------------------
    Description: 
Currently, Hibernate test job fails because of execution timeout [1]. After 
IGNITE-20579 {{HibernateL2CacheSelfTest}} fails with an error and then hangs:
{code}
class org.apache.ignite.IgniteException: Transaction spans operations on atomic 
cache (don't use atomic cache inside a transaction). Since 2.15.0 atomic 
operations inside transactions are not allowed by default. Since 2.16.0 atomic 
operations inside transactions are finally forbidden.
{code}

As we can see, these problem occur because of ATOMIC caches for Hibernate 
regions "default-query-results-region" and "default-update-timestamps-region" 
[2], but problem can be deeper, because these regions are used under the hood 
by the Hibernate itself *_for query and entity caching_*.

*Links:*
# 
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Hibernate?mode=branches#all-projects
# 
https://github.com/apache/ignite-extensions/blob/master/modules/hibernate-ext/hibernate/src/test/java/org/apache/ignite/cache/hibernate/HibernateL2CacheSelfTest.java#L429

  was:
Currently, Hibernate test job fails because of execution timeout [1]. After 
IGNITE-20579 {{HibernateL2CacheSelfTest}} fails with an error and then hangs:
{code}
class org.apache.ignite.IgniteException: Transaction spans operations on atomic 
cache (don't use atomic cache inside a transaction). Since 2.15.0 atomic 
operations inside transactions are not allowed by default. Since 2.16.0 atomic 
operations inside transactions are finally forbidden.
{code}

As we can see, these problem occur because of ATOMIC caches for Hibernate 
regions "default-query-results-region" and "default-update-timestamps-region" 
[2], but problem can be deeper, because these regions are used under the hood 
by the Hibernate itself *_for query caching_*.

*Links:*
# 
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Hibernate?mode=branches#all-projects
# 
https://github.com/apache/ignite-extensions/blob/master/modules/hibernate-ext/hibernate/src/test/java/org/apache/ignite/cache/hibernate/HibernateL2CacheSelfTest.java#L429


> hibernate-ext: "default-query-results-region" and 
> "default-update-timestamps-region" should not be atomic
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-20799
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20799
>             Project: Ignite
>          Issue Type: Test
>          Components: extensions
>            Reporter: Ilya Shishkov
>            Assignee: Ilya Shishkov
>            Priority: Minor
>              Labels: ise
>
> Currently, Hibernate test job fails because of execution timeout [1]. After 
> IGNITE-20579 {{HibernateL2CacheSelfTest}} fails with an error and then hangs:
> {code}
> class org.apache.ignite.IgniteException: Transaction spans operations on 
> atomic cache (don't use atomic cache inside a transaction). Since 2.15.0 
> atomic operations inside transactions are not allowed by default. Since 
> 2.16.0 atomic operations inside transactions are finally forbidden.
> {code}
> As we can see, these problem occur because of ATOMIC caches for Hibernate 
> regions "default-query-results-region" and "default-update-timestamps-region" 
> [2], but problem can be deeper, because these regions are used under the hood 
> by the Hibernate itself *_for query and entity caching_*.
> *Links:*
> # 
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Hibernate?mode=branches#all-projects
> # 
> https://github.com/apache/ignite-extensions/blob/master/modules/hibernate-ext/hibernate/src/test/java/org/apache/ignite/cache/hibernate/HibernateL2CacheSelfTest.java#L429



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to