[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7088?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-7088:
--------------------------------------
Fix Version/s: 9.0.0.Final
> 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, 9.0.0.Final
>
>
> 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
[JBoss JIRA] (ISPN-7088) Interceptors should not access TransactionManager
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7088?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-7088:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> 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, 9.0.0.Final
>
>
> 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
[JBoss JIRA] (ISPN-7089) SingleFileCacheStore; Metadata is sometimes corrupted
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7089?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-7089:
-------------------------------------
Assignee: Galder Zamarreño
> SingleFileCacheStore; Metadata is sometimes corrupted
> -----------------------------------------------------
>
> Key: ISPN-7089
> URL: https://issues.jboss.org/browse/ISPN-7089
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.2.2.Final
> Reporter: Elias Ross
> Assignee: Galder Zamarreño
>
> Over time I have observed the following exceptions:
> 2016-10-06 15:40:26.261 [level=ERROR] - java.io.IOException: Unsupported protocol version 163
> org.infinispan.persistence.spi.PersistenceException: java.io.IOException: Unsupported protocol version 163
> at org.infinispan.marshall.core.MarshalledEntryImpl.unmarshall(MarshalledEntryImpl.java:116) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.marshall.core.MarshalledEntryImpl.getMetadata(MarshalledEntryImpl.java:72) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.persistence.PersistenceUtil.loadAndCheckExpiration(PersistenceUtil.java:120) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.persistence.PersistenceUtil.lambda$loadAndStoreInDataContainer$0(PersistenceUtil.java:98) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.container.DefaultDataContainer.lambda$compute$3(DefaultDataContainer.java:325) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8.compute(BoundedEquivalentConcurrentHashMapV8.java:3600) ~[org.infinispan-infinispan-commons-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:324) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.persistence.PersistenceUtil.loadAndStoreInDataContainer(PersistenceUtil.java:91) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.interceptors.CacheLoaderInterceptor.loadInContext(CacheLoaderInterceptor.java:371) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:366) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.interceptors.CacheLoaderInterceptor.visitDataCommand(CacheLoaderInterceptor.java:187) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.interceptors.CacheLoaderInterceptor.visitGetKeyValueCommand(CacheLoaderInterceptor.java:141) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
> This seems to happen fairly regularly on a number of different hosts.
> The invalid version values seem to change.
> I'm wondering if there is a race condition in how the data is stored, and in particular the metadata.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ISPN-7089) SingleFileCacheStore; Metadata is sometimes corrupted
by Elias Ross (JIRA)
Elias Ross created ISPN-7089:
--------------------------------
Summary: SingleFileCacheStore; Metadata is sometimes corrupted
Key: ISPN-7089
URL: https://issues.jboss.org/browse/ISPN-7089
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.2.2.Final
Reporter: Elias Ross
Over time I have observed the following exceptions:
2016-10-06 15:40:26.261 [level=ERROR] - java.io.IOException: Unsupported protocol version 163
org.infinispan.persistence.spi.PersistenceException: java.io.IOException: Unsupported protocol version 163
at org.infinispan.marshall.core.MarshalledEntryImpl.unmarshall(MarshalledEntryImpl.java:116) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.marshall.core.MarshalledEntryImpl.getMetadata(MarshalledEntryImpl.java:72) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.persistence.PersistenceUtil.loadAndCheckExpiration(PersistenceUtil.java:120) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.persistence.PersistenceUtil.lambda$loadAndStoreInDataContainer$0(PersistenceUtil.java:98) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.container.DefaultDataContainer.lambda$compute$3(DefaultDataContainer.java:325) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8.compute(BoundedEquivalentConcurrentHashMapV8.java:3600) ~[org.infinispan-infinispan-commons-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:324) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.persistence.PersistenceUtil.loadAndStoreInDataContainer(PersistenceUtil.java:91) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.interceptors.CacheLoaderInterceptor.loadInContext(CacheLoaderInterceptor.java:371) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:366) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.interceptors.CacheLoaderInterceptor.visitDataCommand(CacheLoaderInterceptor.java:187) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.interceptors.CacheLoaderInterceptor.visitGetKeyValueCommand(CacheLoaderInterceptor.java:141) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43) ~[org.infinispan-infinispan-core-8.2.2.Final.jar:8.2.2.Final]
This seems to happen fairly regularly on a number of different hosts.
The invalid version values seem to change.
I'm wondering if there is a race condition in how the data is stored, and in particular the metadata.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[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 updated ISPRK-32:
-----------------------------------
Status: Open (was: New)
> 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