September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3565) AS persistence modules still refer to "cachestore"

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3565?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3565: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2112 > AS persistence modules still refer to "cachestore" > -------------------------------------------------- > > Key: ISPN-3565 > URL: https://issues.jboss.org/browse/ISPN-3565 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta2 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3183) HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3183?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3183: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod RollUps from 5.2 to 5.3 -- target can't obtain formerly stored data from RCS > ----------------------------------------------------------------------------------- > > Key: ISPN-3183 > URL: https://issues.jboss.org/browse/ISPN-3183 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Tristan Tarrant > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2 > > Attachments: 52to52sourceTrace, 52to52targetTrace, 52to53sourceTrace, 52to53targetTrace > > > Scenario (typical for rollups): > Start source node, put entries. > Start target node which is pointing to source (source is his RemoteCacheStore now) and try to get entries. > For 5.2 to 5.2 working perfectly. > For 5.2 source and 5.3 target -- we have problems here. > Sorry that I can't provide any valuable info beside TRACEs. > 4 TRACE logs -- rollups from 5.2 to 5.2 source log and target log + rollups from 5.2 to 5.3 source log and target log. > Very quick summary: > 5.2 to 5.2 on target: Entry exists in loader? true > 5.2 to 5.3 on targer: > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Exists in context? null > 16:21:41,508 TRACE [org.infinispan.container.EntryFactoryImpl] (HotRodServerWorker-2) Retrieved from container null > What changed in RemoteCacheStore. What changed in HotRod? Any idea? Let me know, thank you! > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3541) Common store attributes(e.g. purge) are ignored for non-generic stores (file-store, remote etc)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3541?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3541: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Common store attributes(e.g. purge) are ignored for non-generic stores (file-store, remote etc) > ------------------------------------------------------------------------------------------------ > > Key: ISPN-3541 > URL: https://issues.jboss.org/browse/ISPN-3541 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Beta1 > Reporter: Jakub Markos > Assignee: Mircea Markus > Fix For: 6.0.0.Beta2 > > > When using this configuration (notice the purge=true) > {code:xml} > <local-cache name="default" start="EAGER" batching="false"> > <file-store name="hello" > passivation="true" > relative-to="temp" > path="${cachestore.name}" > purge="true"/> > </local-cache> > {code} > and running this test > {code} > for (int i = 0; i < 3; i++) { > cache.put("k" + i, i); > } > controller.stop(CONTAINER); // stops the server > controller.start(CONTAINER); > for (int i = 0; i < 3; i++) { > System.out.println("k" + i + ": " + cache.get("k" + i)); > } > {code} > the entries can be read even after server restart: > {quote} > k0: 0 // expecting null here > k1: 1 // expecting null here > k2: 2 // expecting null here > {quote} > Worked fine with DR4, not with ER1. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3566) Add tests for the custom collections

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3566: ----------------------------------- Summary: Add tests for the custom collections Key: ISPN-3566 URL: https://issues.jboss.org/browse/ISPN-3566 Project: Infinispan Issue Type: Task Reporter: Mircea Markus Assignee: Mircea Markus ISPN-3564 reports a very severe bug in EquivalentLinkedHashMap, would be good to have tests for all our custom collections as bugs in that area might cause lots of pain. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3566) Add tests for the custom collections

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3566?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3566: -------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > Add tests for the custom collections > ------------------------------------- > > Key: ISPN-3566 > URL: https://issues.jboss.org/browse/ISPN-3566 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Galder Zamarreño > > ISPN-3564 reports a very severe bug in EquivalentLinkedHashMap, would be good to have tests for all our custom collections as bugs in that area might cause lots of pain. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3566) Add tests for the custom collections

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3566?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3566: -------------------------------- Priority: Critical (was: Major) > Add tests for the custom collections > ------------------------------------- > > Key: ISPN-3566 > URL: https://issues.jboss.org/browse/ISPN-3566 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Priority: Critical > > ISPN-3564 reports a very severe bug in EquivalentLinkedHashMap, would be good to have tests for all our custom collections as bugs in that area might cause lots of pain. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3507) EntrySet operation in cache with LevelDB store ignores expiration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3507?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3507: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > EntrySet operation in cache with LevelDB store ignores expiration > ----------------------------------------------------------------- > > Key: ISPN-3507 > URL: https://issues.jboss.org/browse/ISPN-3507 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Alpha4 > Reporter: Michal Linhard > Assignee: Mircea Markus > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2 > > > In cache with leveldb cache store, expired entry still appears in collection returned by entrySet operation. > test: > https://github.com/mlinhard/infinispan-cachestore-leveldb/commit/71b62c19... -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3398) Unmarshall problem in compatibility mode

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3398?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3398: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Unmarshall problem in compatibility mode > ---------------------------------------- > > Key: ISPN-3398 > URL: https://issues.jboss.org/browse/ISPN-3398 > Project: Infinispan > Issue Type: Bug > Components: Marshalling, Remote protocols, Server > Affects Versions: 5.3.0.Final, 6.0.0.Alpha2 > Reporter: Michal Linhard > Assignee: Pedro Ruivo > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2, 6.0.0.Final > > > JDG 6.2.0.DR2 client/server tests using hotrod and cache in compatibility mode: > throw this: > {code} > 04:48:28,445 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread-0) ISPN000136: Execution error: java.io.IOException: Unsupported protocol version 9 > at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1243) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.startObjectInput(AbstractJBossMarshaller.java:138) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromByteBuffer(AbstractJBossMarshaller.java:119) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commons.marshall.AbstractMarshaller.objectFromByteBuffer(AbstractMarshaller.java:83) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.server.hotrod.HotRodTypeConverter.unmarshall(HotRodTypeConverter.scala:36) [infinispan-server-hotrod-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.server.hotrod.HotRodTypeConverter.boxValue(HotRodTypeConverter.scala:22) [infinispan-server-hotrod-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.compat.TypeConverterInterceptor.visitPutKeyValueCommand(TypeConverterInterceptor.java:72) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:106) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:70) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:321) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:39) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:97) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.access$000(InboundInvocationHandlerImpl.java:46) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl$2.run(InboundInvocationHandlerImpl.java:169) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > the exception appears for each request, the form is always > "Unsupported protocol version X" where X differs > see > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/PERF-CS/jo... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/PERF-CS/jo... -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3140) JMX operation to suppress state transfer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3140?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3140: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 974402|https://bugzilla.redhat.com/show_bug.cgi?id=974402] from ON_QA to ASSIGNED > JMX operation to suppress state transfer > ---------------------------------------- > > Key: ISPN-3140 > URL: https://issues.jboss.org/browse/ISPN-3140 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache, State transfer > Affects Versions: 5.2.6.Final > Reporter: Manik Surtani > Assignee: Dan Berindei > Fix For: 5.2.7.Final, 5.3.0.CR2, 5.3.0.Final > > > This feature request is to expose a JMX operation on each node, to suppress state transfer for a period of time. This flag would be {{false}} by default. > The use case of this flag would be to ease bringing down (and up) a cluster for maintenance work. A typical workflow would be: > 1) Shut down application requests to the data grid > 2) Suppress state transfer on all nodes via JMX > 3) Bring down all nodes > 4) Perform maintenance work > 5) Bring up nodes, one at a time. As each node comes up, disable state transfer for the node via JMX. > 6) Once all nodes are up, enable state transfer for each node again via JMX > 7) Allow application requests to reach the grid again. > The purpose of this is to allow smooth and fast shutdown and startup, remove the risk of OOM errors (when bringing a grid down). > This is a small but useful subset of full manual state transfer as defined in ISPN-1394. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3373) HotRod topology cache should allow disabling awaitInitialTransfer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3373?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3373: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 974402|https://bugzilla.redhat.com/show_bug.cgi?id=974402] Tested for ER1 and still the issue described above appears. > HotRod topology cache should allow disabling awaitInitialTransfer > ----------------------------------------------------------------- > > Key: ISPN-3373 > URL: https://issues.jboss.org/browse/ISPN-3373 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols, Server > Affects Versions: 6.0.0.Alpha1 > Reporter: NadirX > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2 > > > When a server with a hotrod endpoint joins a cluster where state transfer has been disabled (ISPN-3140), waiting for initial state transfer should also be disabled on the topology cache, otherwise failures occur. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2013