[JBoss JIRA] (ISPN-5691) Server should enable writeSkew for some configurations by default
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5691:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1255783|https://bugzilla.redhat.com/show_bug.cgi?id=1255783] from ON_QA to VERIFIED
> Server should enable writeSkew for some configurations by default
> -----------------------------------------------------------------
>
> Key: ISPN-5691
> URL: https://issues.jboss.org/browse/ISPN-5691
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Galder Zamarreño
> Assignee: Tristan Tarrant
> Fix For: 8.1.0.Alpha2, 8.1.0.Final, 7.2.6.Final
>
>
> By default, optimistic locking caches do not enable write skew. This was already spotted in ISPN-3655.
> In an embedded environment, the user can always enable write skew in its configuration, but this cannot be enabled in server mode.
> Widlfly does enable write skew programmatically depending on the configuration:
> {quote}
> > hey, quick q: can you configure writeSkew on infinispan wildfly
> config?
> <pferraro> we always enable write skew for synchronous, optimistic,
> repeatable-read caches, and disable otherwise
> > pferraro: ah, you do it in the integration code?
> <pferraro> yes
> {quote}
> We need to be doing the same in server configuration, otherwise we run the risk of having issues with conditional operations under failure situations (see ISPN-2956)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5863) Default metadata not merged for DecoratedCache operations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5863:
-----------------------------------------------
Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272052|https://bugzilla.redhat.com/show_bug.cgi?id=1272052] from ON_QA to VERIFIED
> Default metadata not merged for DecoratedCache operations
> ---------------------------------------------------------
>
> Key: ISPN-5863
> URL: https://issues.jboss.org/browse/ISPN-5863
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta1
>
>
> If the ISPN server cache is configured with expiration like:
> <cache-container name="local" default-cache="default" statistics="true">
> <state-persistence/>
> <local-cache name="default" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <expiration lifespan="1000" interval="20000"/>
> </local-cache>
> The entry should automatic expired in 1second after it is added.
> But a client still have the key
> - after 1 sec where it should have been expired
> - after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5854) NonTxInvalidationInterceptor added twice to cache used for Hibernate 2LC
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-5854?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-5854:
-----------------------------------
Please, post a link to Hibernate issue when you create it.
> NonTxInvalidationInterceptor added twice to cache used for Hibernate 2LC
> ------------------------------------------------------------------------
>
> Key: ISPN-5854
> URL: https://issues.jboss.org/browse/ISPN-5854
> Project: Infinispan
> Issue Type: Bug
> Components: Integration
> Affects Versions: 7.2.5.Final
> Reporter: Karl von Randow
> Assignee: Galder Zamarreño
>
> I use the same Infinispan cache for multiple Hibernate entities. The {{PutFromLoadValidator}} looks for and replaces the {{InvalidationInterceptor}} the first time it sees the cache, but the second time it fails to find the {{InvalidationInterceptor}} and ends up with {{invalidationPosition = 0}} from line 168, which means it incorrectly removes the first interceptor from the chain and then tries to add the {{NonTxInvalidationInterceptor}} again, causing the exception below.
> Perhaps the {{NonTxInvalidationInterceptor}} should only be added once per cache, or the {{accessStrategy}} should be cached or something?
> {noformat}
> org.infinispan.commons.CacheConfigurationException: Detected interceptor of type [org.hibernate.cache.infinispan.access.NonTxInvalidationInterceptor] being added to the interceptor chain 170588969 more than once!
> at org.infinispan.interceptors.InterceptorChain.assertNotAdded(InterceptorChain.java:76)
> at org.infinispan.interceptors.InterceptorChain.addInterceptor(InterceptorChain.java:90)
> at org.infinispan.cache.impl.CacheImpl.addInterceptor(CacheImpl.java:883)
> at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:192)
> at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:133)
> at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.prepareForValidation(BaseTransactionalDataRegion.java:137)
> at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.createAccessDelegate(BaseTransactionalDataRegion.java:122)
> at org.hibernate.cache.infinispan.collection.CollectionRegionImpl.buildAccessStrategy(CollectionRegionImpl.java:49)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:400)
> at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444)
> at org.hibernate.boot.internal.MetadataImpl.buildSessionFactory(MetadataImpl.java:170)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5875) HotRod Client does not handle failover silent when nodes are stopped if using role based authentication
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5875?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5875:
-----------------------------------------------
Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1273137|https://bugzilla.redhat.com/show_bug.cgi?id=1273137] from ON_QA to VERIFIED
> HotRod Client does not handle failover silent when nodes are stopped if using role based authentication
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5875
> URL: https://issues.jboss.org/browse/ISPN-5875
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Security
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: hotrod, hotrod-java-client, security
> Fix For: 8.1.0.Beta1, 8.1.0.Final, 8.0.2.Final
>
>
> A HotRod client fail over silent if one instance is shutting down if there is no Security enabled.
> With role based authentication the client fail sporadically with a WARN message
> {code}WARN: ISPN004005: Error received from the server: java.security.PrivilegedActionException:
> org.infinispan.IllegalLifecycleStateException: ISPN000324: Cache 'testCache' is in 'STOPPING' state and this is an invocation not
> belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate the cache container.
> {code}
> and the following Exception:
> {code}org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[2825] returned server error (status=0x85):
> java.security.PrivilegedActionException: org.infinispan.IllegalLifecycleStateException: ISPN000324: Cache 'testCache' is in 'STOPPING'
> state and this is an invocation not belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate
> the cache container.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:336)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:126)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:112)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:57)
> at org.infinispan.client.hotrod.impl.operations.PutIfAbsentOperation.executeOperation(PutIfAbsentOperation.java:36)
> at org.infinispan.client.hotrod.impl.operations.PutIfAbsentOperation.executeOperation(PutIfAbsentOperation.java:23)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:52)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.putIfAbsent(RemoteCacheImpl.java:257)
> at org.infinispan.client.hotrod.impl.RemoteCacheSupport.putIfAbsent(RemoteCacheSupport.java:54)
> at HotRodTestClient.updateCache(HotRodTestClient.java:69)
> at HotRodTestClient.lambda$queuePut$0(HotRodTestClient.java:88)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5791) Query DSL : Projecting a Date field multiple times will render it as string
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5791?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5791:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1277075|https://bugzilla.redhat.com/show_bug.cgi?id=1277075] from ON_QA to VERIFIED
> Query DSL : Projecting a Date field multiple times will render it as string
> ---------------------------------------------------------------------------
>
> Key: ISPN-5791
> URL: https://issues.jboss.org/browse/ISPN-5791
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta1, 8.0.2.Final
>
>
> Adding this in QueryDslConditionsTest fails. The second date projection is a String instead of being a Date. First projection is OK. The problem is gone if cache is not indexed, which makes me think it is more of a problem in CacheQuery.
> {code}
> public void testDuplicateDateProjection() throws Exception {
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(getModelFactory().getTransactionImplClass())
> .select("id", "date", "date")
> .having("description").eq("Hotel")
> .toBuilder().build();
> List<Object[]> list = q.list();
> assertEquals(1, list.size());
> assertEquals(1, list.size());
> assertEquals(3, list.get(0).length);
> assertEquals(3, list.get(0)[0]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[1]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[2]);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months