July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3293) Putting entries with memcached is ignoring the queue-flush-interval parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3293?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3293: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> made a comment on [bug 987520|https://bugzilla.redhat.com/show_bug.cgi?id=987520] Please see the linked JIRA for more information. > Putting entries with memcached is ignoring the queue-flush-interval parameter > ----------------------------------------------------------------------------- > > Key: ISPN-3293 > URL: https://issues.jboss.org/browse/ISPN-3293 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Jakub Markos > Assignee: Tristan Tarrant > Attachments: server1.log, server2.log > > > I have a cluster of 2 nodes with the following configuration: > {code:xml} > <replicated-cache name="memcachedCache" > start="EAGER" > mode="ASYNC" > batching="false" > queue-size="1000" > queue-flush-interval="15000"> > </replicated-cache> > {code} > The following code (MemcachedHelper is a memcached client) > {code} > mc1 = new MemcachedHelper(server1.getMemcachedEndpoint().getInetAddress().getHostName(), server1.getMemcachedEndpoint().getPort()); > mc2 = new MemcachedHelper(server2.getMemcachedEndpoint().getInetAddress().getHostName(), server2.getMemcachedEndpoint().getPort()); > mc1.set("key1", "value1"); > assertTrue(null != mc1.get("key1")); > assertTrue(null == mc2.get("key1")); > {code} > fails on the 2nd assert, because the entry is retrieved. > According to logs (attached), the replication queue is correctly flushed after 15 seconds with 1 element (and happens after the gets). > Works correctly with hotrod (entry is replicated only after the flush happens). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3355) Add support for clustered listeners

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3355: ----------------------------------- Summary: Add support for clustered listeners Key: ISPN-3355 URL: https://issues.jboss.org/browse/ISPN-3355 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus As opposed to the current listener approach in Infinispan ( a listener instance is invoked on the data owners ), this JIRA is about adding support for a cluster listener: the same listener instance that is notified disregarding of data ownership ( RPC calls involved). Due to the fact that the listener notification might involve an RPC, it is nice to be able to specify filters on these listeners. The clustered listener support opens the way for some interesting architectures: * persistent/continuous queries: the query is transformed in a filter. On each notification, the listener (stateful) updates the query state * simplistic CEP can be built on top of the persistent query described above * remote/hotrod notifications might be based on clustered listeners as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3354) Multiple events on the local node with Infinispan 5.3.0-final

by Luca Zenti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3354?page=com.atlassian.jira.plugin.... ] Luca Zenti updated ISPN-3354: ----------------------------- Attachment: TestInfinispanDuplicatedEvents.java A test case reproducing the issue. To run it, junit 4.4 and hamcrest library 1.1 are needed > Multiple events on the local node with Infinispan 5.3.0-final > ------------------------------------------------------------- > > Key: ISPN-3354 > URL: https://issues.jboss.org/browse/ISPN-3354 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 5.3.0.Final > Reporter: Luca Zenti > Assignee: Mircea Markus > Attachments: TestInfinispanDuplicatedEvents.java > > > After upgrading to Infinispan 5.3.0-final I found a strange "intermittent" problem in my application. Digging a bit deeper, I found out it is due to CacheEntry events raised twice for some keys on the local node (the node where the cache operation is invoked). > I was able to reproduce the problem and I wrote the attached test case. > The problem happens regardless of the cluster mode, but only with non-transactional caches. I think this is due to the fact that with transactional caches the events are raised on commit. > Also, my application used to work with an interceptor rather than an event listener, so I actually found the problem when I saw my interceptor being occasionally executed 3 times with 2 nodes. > I'm not sure whether the command and the chain of interceptor is really meant to be executed twice on the local node, but the consequent behaviour on the events sounds like a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3354) Multiple events on the local node with Infinispan 5.3.0-final

by Luca Zenti (JIRA)

Luca Zenti created ISPN-3354: -------------------------------- Summary: Multiple events on the local node with Infinispan 5.3.0-final Key: ISPN-3354 URL: https://issues.jboss.org/browse/ISPN-3354 Project: Infinispan Issue Type: Bug Components: Listeners Affects Versions: 5.3.0.Final Reporter: Luca Zenti Assignee: Mircea Markus After upgrading to Infinispan 5.3.0-final I found a strange "intermittent" problem in my application. Digging a bit deeper, I found out it is due to CacheEntry events raised twice for some keys on the local node (the node where the cache operation is invoked). I was able to reproduce the problem and I wrote the attached test case. The problem happens regardless of the cluster mode, but only with non-transactional caches. I think this is due to the fact that with transactional caches the events are raised on commit. Also, my application used to work with an interceptor rather than an event listener, so I actually found the problem when I saw my interceptor being occasionally executed 3 times with 2 nodes. I'm not sure whether the command and the chain of interceptor is really meant to be executed twice on the local node, but the consequent behaviour on the events sounds like a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2203?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2203. --------------------------------- Resolution: Done > Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable > ------------------------------------------------------------------- > > Key: ISPN-2203 > URL: https://issues.jboss.org/browse/ISPN-2203 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 6.0.0.Alpha2, 5.3.0.Beta2, 5.2.0.Beta2 > > Attachments: AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle.tar.gz, testAsyncMethodWithLifespanAndMaxIdle-0.log > > > Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2203?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2203: -------------------------------- Assignee: Mircea Markus (was: Tomas Sykora) > Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable > ------------------------------------------------------------------- > > Key: ISPN-2203 > URL: https://issues.jboss.org/browse/ISPN-2203 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.2.0.Beta2, 5.3.0.Beta2, 6.0.0.Alpha2 > > Attachments: AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle.tar.gz, testAsyncMethodWithLifespanAndMaxIdle-0.log > > > Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-506) Infinispan should have a notion of comparable dataversion for handling external db updates

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-506?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-506: --------------------------------------- Since Infinispan 5.3 you can now provide version information externally via a Metadata object. However, this information does not yet survive deletes. There might be more logic needed to be implemented, because the Metadata is just stored alongside the value. This Metadata does not participate in equals comparisons (i.e. replace passing new and old values), and we have not implemented logic to avoid older metadata to replace newer metadata, or use that metadata to figure out if the put is stale or not. We should sync up when we're both in Neuchatel and I can give you an update and get some clarification on what we're missing from ISPN perspective taking in account what I said above. > Infinispan should have a notion of comparable dataversion for handling external db updates > ------------------------------------------------------------------------------------------ > > Key: ISPN-506 > URL: https://issues.jboss.org/browse/ISPN-506 > Project: Infinispan > Issue Type: Feature Request > Reporter: Max Rydahl Andersen > Assignee: Galder Zamarreño > > As discussed in hotel bar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-3311: ---------------------------------------- This is either a Maven bug or is configurable behind some weird, obscure flag: {code}[g@:~/Go/test/infinispan.git]% jar tf lucene/lucene-directory/target/infinispan-lucene-directory.jar | grep META-INF META-INF/MANIFEST.MF META-INF/ META-INF/DEPENDENCIES.txt META-INF/LICENSE.txt META-INF/maven/ META-INF/maven/org.infinispan/ META-INF/maven/org.infinispan/infinispan-lucene-directory/ META-INF/maven/org.infinispan/infinispan-lucene-directory/pom.properties META-INF/maven/org.infinispan/infinispan-lucene-directory/pom.xml [g@:~/Go/test/infinispan.git]% l lucene/lucene-directory/target/classes/META-INF total 80 drwxr-xr-x 7 g staff 238B Jul 23 13:30 . drwxr-xr-x 4 g staff 136B Jul 23 13:39 .. -rw-r--r-- 1 g staff 2.5K Jul 23 13:39 DEPENDENCIES.txt -rw-r--r-- 1 g staff 26K Jul 23 13:39 LICENSE.txt -rw-r--r-- 1 g staff 4.9K Jul 23 13:39 MANIFEST.MF drwxr-xr-x 3 g staff 102B Jul 23 13:30 maven drwxr-xr-x 3 g staff 102B Jul 23 13:29 services [g@:~/Go/test/infinispan.git]% {code} It includes everything except the 'services' subfolder. Can't think of a workaround right now, so gonna debug the Maven code. > org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2203?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2203: -------------------------------- Labels: testsuite_stability (was: ) > Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable > ------------------------------------------------------------------- > > Key: ISPN-2203 > URL: https://issues.jboss.org/browse/ISPN-2203 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Tomas Sykora > Labels: testsuite_stability > Fix For: 5.2.0.Beta2, 5.3.0.Beta2 > > Attachments: AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle.tar.gz, testAsyncMethodWithLifespanAndMaxIdle-0.log > > > Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2203?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2203: -------------------------------- Fix Version/s: 6.0.0.Alpha2 > Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable > ------------------------------------------------------------------- > > Key: ISPN-2203 > URL: https://issues.jboss.org/browse/ISPN-2203 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Tomas Sykora > Labels: testsuite_stability > Fix For: 5.2.0.Beta2, 5.3.0.Beta2, 6.0.0.Alpha2 > > Attachments: AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle.tar.gz, testAsyncMethodWithLifespanAndMaxIdle-0.log > > > Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 July 2013