October 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPRK-32) Incorrect test reports generated

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-32?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes commented on ISPRK-32: ---------------------------------------- Related: https://github.com/scalatest/scalatest/issues/916 > Incorrect test reports generated > -------------------------------- > > Key: ISPRK-32 > URL: https://issues.jboss.org/browse/ISPRK-32 > Project: Infinispan Spark > Issue Type: Bug > Components: Testsuite > Reporter: Gustavo Fernandes > > Currently test reports are meaningless since they only carry the name of the suite: > {code:xml} > ... > <testcase classname="org.infinispan.spark.ClusteredSuites" name="(It is not a test)" time="2.034"> > <testcase classname="org.infinispan.spark.ClusteredSuites" name="(It is not a test)" time="1.474"> > ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-32) Incorrect test reports generated

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPRK-32: -------------------------------------- Summary: Incorrect test reports generated Key: ISPRK-32 URL: https://issues.jboss.org/browse/ISPRK-32 Project: Infinispan Spark Issue Type: Bug Components: Testsuite Reporter: Gustavo Fernandes Currently test reports are meaningless since they only carry the name of the suite: {code:xml} ... <testcase classname="org.infinispan.spark.ClusteredSuites" name="(It is not a test)" time="2.034"> <testcase classname="org.infinispan.spark.ClusteredSuites" name="(It is not a test)" time="1.474"> ... {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7088?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7088: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4604 > Interceptors should not access TransactionManager > ------------------------------------------------- > > Key: ISPN-7088 > URL: https://issues.jboss.org/browse/ISPN-7088 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_failure > Fix For: 9.0.0.Beta1 > > > With ISPN-5469, we are no longer executing all the interceptor on the user thread, even on the originator. That means trying to read the thread-local transaction with {{TransactionManager.getTransaction()}} sometimes won't work, so interceptors should avoid it. > E.g. {{InvocationContextInterceptor.markTxForRollbackAndRethrow()}} wants to rollback the current transaction but doesn't find any transaction bound to the current thread, causing failures in {{PessimisticTxPartitionAndMergeDuringRuntimeTest}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7088: ---------------------------------- Summary: Interceptors should not access TransactionManager Key: ISPN-7088 URL: https://issues.jboss.org/browse/ISPN-7088 Project: Infinispan Issue Type: Bug Components: Core Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Beta1 With ISPN-5469, we are no longer executing all the interceptor on the user thread, even on the originator. That means trying to read the thread-local transaction with {{TransactionManager.getTransaction()}} sometimes won't work, so interceptors should avoid it. E.g. {{InvocationContextInterceptor.markTxForRollbackAndRethrow()}} wants to rollback the current transaction but doesn't find any transaction bound to the current thread, causing failures in {{PessimisticTxPartitionAndMergeDuringRuntimeTest}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7088?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7088: ------------------------------- Priority: Critical (was: Major) > Interceptors should not access TransactionManager > ------------------------------------------------- > > Key: ISPN-7088 > URL: https://issues.jboss.org/browse/ISPN-7088 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_failure > Fix For: 9.0.0.Beta1 > > > With ISPN-5469, we are no longer executing all the interceptor on the user thread, even on the originator. That means trying to read the thread-local transaction with {{TransactionManager.getTransaction()}} sometimes won't work, so interceptors should avoid it. > E.g. {{InvocationContextInterceptor.markTxForRollbackAndRethrow()}} wants to rollback the current transaction but doesn't find any transaction bound to the current thread, causing failures in {{PessimisticTxPartitionAndMergeDuringRuntimeTest}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7088?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7088: ------------------------------- Status: Open (was: New) > Interceptors should not access TransactionManager > ------------------------------------------------- > > Key: ISPN-7088 > URL: https://issues.jboss.org/browse/ISPN-7088 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_failure > Fix For: 9.0.0.Beta1 > > > With ISPN-5469, we are no longer executing all the interceptor on the user thread, even on the originator. That means trying to read the thread-local transaction with {{TransactionManager.getTransaction()}} sometimes won't work, so interceptors should avoid it. > E.g. {{InvocationContextInterceptor.markTxForRollbackAndRethrow()}} wants to rollback the current transaction but doesn't find any transaction bound to the current thread, causing failures in {{PessimisticTxPartitionAndMergeDuringRuntimeTest}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7087) Handle ClientCacheEntryExpired into InvalidatedNearCacheListener

by Jean-Francois LARTAUD (JIRA)

[ https://issues.jboss.org/browse/ISPN-7087?page=com.atlassian.jira.plugin.... ] Jean-Francois LARTAUD updated ISPN-7087: ---------------------------------------- Description: Hi, Is there a reason why the InvalidatedNearCacheListener does not support the cache entry expiration ? By adding the ClientCacheEntryExpired annotation on the listener, it should be possible to invalidate a near cache entry when it has expired on a remote infinispan server. For example, into org.infinispan.client.hotrod.near.NearCacheService.InvalidatedNearCacheListener add this method : {code} @ClientCacheEntryExpired @SuppressWarnings("unused") public void handleExpiredEvent(ClientCacheEntryExpiredEvent<K> event) { invalidate(event.getKey()); } {code} Thanks, was: Hi, Is there a reason why the InvalidatedNearCacheListener does not support the cache entry expiration ? By adding the ClientCacheEntryExpired annotation on the listener, it should be possible to invalidate a near cache entry when it is expired on a remote server. For example, into org.infinispan.client.hotrod.near.NearCacheService.InvalidatedNearCacheListener add this method : {code} @ClientCacheEntryExpired @SuppressWarnings("unused") public void handleExpiredEvent(ClientCacheEntryExpiredEvent<K> event) { invalidate(event.getKey()); } {code} Thanks, > Handle ClientCacheEntryExpired into InvalidatedNearCacheListener > ---------------------------------------------------------------- > > Key: ISPN-7087 > URL: https://issues.jboss.org/browse/ISPN-7087 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 8.2.4.Final > Reporter: Jean-Francois LARTAUD > > Hi, > Is there a reason why the InvalidatedNearCacheListener does not support the cache entry expiration ? > By adding the ClientCacheEntryExpired annotation on the listener, it should be possible to invalidate a near cache entry when it has expired on a remote infinispan server. > For example, into org.infinispan.client.hotrod.near.NearCacheService.InvalidatedNearCacheListener add this method : > {code} > @ClientCacheEntryExpired > @SuppressWarnings("unused") > public void handleExpiredEvent(ClientCacheEntryExpiredEvent<K> event) { > invalidate(event.getKey()); > } > {code} > Thanks, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7087) Handle ClientCacheEntryExpired into InvalidatedNearCacheListener

by Jean-Francois LARTAUD (JIRA)

Jean-Francois LARTAUD created ISPN-7087: ------------------------------------------- Summary: Handle ClientCacheEntryExpired into InvalidatedNearCacheListener Key: ISPN-7087 URL: https://issues.jboss.org/browse/ISPN-7087 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Affects Versions: 8.2.4.Final Reporter: Jean-Francois LARTAUD Hi, Is there a reason why the InvalidatedNearCacheListener does not support the cache entry expiration ? By adding the ClientCacheEntryExpired annotation on the listener, it should be possible to invalidate a near cache entry when it is expired on a remote server. For example, into org.infinispan.client.hotrod.near.NearCacheService.InvalidatedNearCacheListener add this method : {code} @ClientCacheEntryExpired @SuppressWarnings("unused") public void handleExpiredEvent(ClientCacheEntryExpiredEvent<K> event) { invalidate(event.getKey()); } {code} Thanks, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7007) Refactor the AS modules into one package

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7007?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7007: ------------------------------------ Status: Open (was: New) > Refactor the AS modules into one package > ---------------------------------------- > > Key: ISPN-7007 > URL: https://issues.jboss.org/browse/ISPN-7007 > Project: Infinispan > Issue Type: Task > Components: WildFly modules > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Final > > > - remove as-modules/client > - move as-modules/embedded to become as-modules > - for symmetry with the uberjars, have an org.infinispan.embedded and org.infinispan.remote modules which re-export the appropriate APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7007) Refactor the AS modules into one package

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7007?page=com.atlassian.jira.plugin.... ] Work on ISPN-7007 started by Gustavo Fernandes. ----------------------------------------------- > Refactor the AS modules into one package > ---------------------------------------- > > Key: ISPN-7007 > URL: https://issues.jboss.org/browse/ISPN-7007 > Project: Infinispan > Issue Type: Task > Components: WildFly modules > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Final > > > - remove as-modules/client > - move as-modules/embedded to become as-modules > - for symmetry with the uberjars, have an org.infinispan.embedded and org.infinispan.remote modules which re-export the appropriate APIs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2016