December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2612) Problem broadcasting CH_UPDATE command

by Michal Linhard (JIRA)

Michal Linhard created ISPN-2612: ------------------------------------ Summary: Problem broadcasting CH_UPDATE command Key: ISPN-2612 URL: https://issues.jboss.org/browse/ISPN-2612 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 5.2.0.Beta5 Reporter: Michal Linhard Assignee: Mircea Markus Infinispan 5.2.0.Beta5 JGroups 3.2.4.Final Steps to reproduce (I'm using two virtual interfaces test1, test2) 1. Start org.jboss.qa.jdg.Test with -Djgroups.udp.bind_addr=test1 -Djava.net.preferIPv4Stack=true 2. wait 10 sec 3. Start org.jboss.qa.jdg.Test with -Djgroups.udp.bind_addr=test2 -Djava.net.preferIPv4Stack=true After 5 seconds there should be this timeout exception: {code} 19:42:14,146 WARN [org.infinispan.topology.CacheTopologyControlCommand] (OOB-2,mlinhard-work-37329) ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=___defaultcache, type=REBALANCE_CONFIRM, sender=mlinhard-work-47337, joinInfo=null, topologyId=1, currentCH=null, pendingCH=null, throwable=null, viewId=1} java.util.concurrent.ExecutionException: org.infinispan.CacheException: org.jgroups.TimeoutException: TimeoutException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232) at java.util.concurrent.FutureTask.get(FutureTask.java:91) at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:563) at org.infinispan.topology.ClusterTopologyManagerImpl.broadcastConsistentHashUpdate(ClusterTopologyManagerImpl.java:349) at org.infinispan.topology.ClusterTopologyManagerImpl.handleRebalanceCompleted(ClusterTopologyManagerImpl.java:213) at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:160) at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:137) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromLocalCluster(CommandAwareRpcDispatcher.java:252) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:219) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:483) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:390) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:248) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:598) at org.jgroups.JChannel.up(JChannel.java:703) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1020) at org.jgroups.protocols.RSVP.up(RSVP.java:172) at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:896) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:736) at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:414) at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:606) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:187) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) at org.jgroups.protocols.Discovery.up(Discovery.java:359) at org.jgroups.protocols.TP.passMessageUp(TP.java:1287) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1850) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1823) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.infinispan.CacheException: org.jgroups.TimeoutException: TimeoutException at org.infinispan.util.Util.rewrapAsCacheException(Util.java:532) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:152) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:518) at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:545) at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:542) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) ... 3 more Caused by: org.jgroups.TimeoutException: TimeoutException at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:145) at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:40) at org.jgroups.util.AckCollector.waitForAllAcks(AckCollector.java:93) at org.jgroups.protocols.RSVP$Entry.block(RSVP.java:287) at org.jgroups.protocols.RSVP.down(RSVP.java:118) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1025) at org.jgroups.JChannel.down(JChannel.java:718) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:616) at org.jgroups.blocks.RequestCorrelator.sendRequest(RequestCorrelator.java:173) at org.jgroups.blocks.GroupRequest.sendRequest(GroupRequest.java:360) at org.jgroups.blocks.GroupRequest.sendRequest(GroupRequest.java:103) at org.jgroups.blocks.Request.execute(Request.java:83) at org.jgroups.blocks.MessageDispatcher.cast(MessageDispatcher.java:335) at org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:249) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processCalls(CommandAwareRpcDispatcher.java:330) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:145) ... 8 more {code} Analysis: These are the messages sent after view change: {code} test1 test2 <--- JOIN ---- ---- REBALANCE_START ---> <--- StateRequestCommand ---- ---- StateResponseCommand ---> <--- REBALANCE_CONFIRM ---- ---- CH_UPDATE ---> {code} The last CH_UPDATE message is broadcast, test2 successfully processes it, but test1 stays in waiting state, because it for some reason awaits response also from itself - local variable entry in the method RSVP.down (https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/...) contained local address. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2611) Drop rhq-pluginAnnotations and rhq-pluginGen dependencies

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2611?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2611: ---------------------------------- Priority: Minor (was: Major) > Drop rhq-pluginAnnotations and rhq-pluginGen dependencies > --------------------------------------------------------- > > Key: ISPN-2611 > URL: https://issues.jboss.org/browse/ISPN-2611 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Mircea Markus > Priority: Minor > Fix For: 5.2.0.CR1 > > > The rhq-pluginAnnotations and rhq-pluginGen dependencies should be dropped since we can generate the required RHQ plugin descriptor using our own ManagedOperation and ManagedAttribute annotations. > This will also remove the requirement to carry rhq-pluginAnnotations around to workaround a Java compiler 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2272) Migrate deprecated configuration API in tests infinispan-core

by Thomas Fromm (JIRA)

[ https://issues.jboss.org/browse/ISPN-2272?page=com.atlassian.jira.plugin.... ] Thomas Fromm reassigned ISPN-2272: ---------------------------------- Assignee: Navin Surtani (was: Thomas Fromm) > Migrate deprecated configuration API in tests infinispan-core > ------------------------------------------------------------- > > Key: ISPN-2272 > URL: https://issues.jboss.org/browse/ISPN-2272 > Project: Infinispan > Issue Type: Sub-task > Components: Test Suite > Affects Versions: 5.2.0.Alpha3 > Reporter: Thomas Fromm > Assignee: Navin Surtani > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2611) Drop rhq-pluginAnnotations and rhq-pluginGen dependencies

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2611: ------------------------------------- Summary: Drop rhq-pluginAnnotations and rhq-pluginGen dependencies Key: ISPN-2611 URL: https://issues.jboss.org/browse/ISPN-2611 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Mircea Markus Fix For: 5.2.0.CR1 The rhq-pluginAnnotations and rhq-pluginGen dependencies should be dropped since we can generate the required RHQ plugin descriptor using our own ManagedOperation and ManagedAttribute annotations. This will also remove the requirement to carry rhq-pluginAnnotations around to workaround a Java compiler 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2610) Use Query but disable automatic indexing

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2610: ------------------------------------- Summary: Use Query but disable automatic indexing Key: ISPN-2610 URL: https://issues.jboss.org/browse/ISPN-2610 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.2.0.Beta6, 5.2.0.Final The option known in Hibernate Search as "hibernate.search.default.indexing_strategy" value="manual" is not applied by Infinispan Query. Workaround: use the SKIP_INDEXING flag {code} org.infinispan.context.Flag.SKIP_INDEXING{code} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2591) Upgrade Server to Infinispan 5.2.0.Beta5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2591?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-2591: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=884793 > Upgrade Server to Infinispan 5.2.0.Beta5 > ---------------------------------------- > > Key: ISPN-2591 > URL: https://issues.jboss.org/browse/ISPN-2591 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2591) Upgrade Server to Infinispan 5.2.0.Beta5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2591?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2591: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 884793|https://bugzilla.redhat.com/show_bug.cgi?id=884793] from NEW to MODIFIED > Upgrade Server to Infinispan 5.2.0.Beta5 > ---------------------------------------- > > Key: ISPN-2591 > URL: https://issues.jboss.org/browse/ISPN-2591 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2566) TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2566: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] from ON_QA to ON_DEV > TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly > ------------------------------------------------------------------------------- > > Key: ISPN-2566 > URL: https://issues.jboss.org/browse/ISPN-2566 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.Beta4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.Beta6, 5.2.0.Final > > > Say we have a topology-aware cache with numOwners = 2 and two nodes: A(machine=m1) and B(machine=m1). When node C(machine=m2) joins, it should own every key, either as a primary or as a backup owner. This doesn't happen, node C owns just as many segments as nodes A and B. > Example: > {noformat} > 19:21:17,295 TRACE [org.infinispan.topology.ClusterTopologyManagerImpl] (undefined) Updating cache topology topology for rebalance: > CacheTopology{id=3, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1, > 32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 1 0, 68: 1 0, 69: 1 0, 70: 1 0, 71: 1 0, > 72: 1 0, 73: 1 0, 74: 1 0, 75: 1 0, 76: 1 0, 77: 1 0, 78: 1 0, 79: 1 0}, > pendingCH=DefaultConsistentHash{numSegments=80, numOwners=2, > members=[node0/default(primary), node1/default(primary), node2/default(secondary)], > owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1, > 8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1, > 16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1, > 24: 0 1, 25: 0 1, 26: 0 1, 27: 2 0, 28: 2 0, 29: 2 0, 30: 2 0, 31: 2 0, > 32: 2 0, 33: 2 0, 34: 2 0, 35: 2 0, 36: 2 0, 37: 2 0, 38: 2 0, 39: 2 0, > 40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0, > 48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0, > 56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0, > 64: 1 0, 65: 1 0, 66: 1 0, 67: 2 1, 68: 2 1, 69: 2 1, 70: 2 1, 71: 2 1, > 72: 2 1, 73: 2 1, 74: 2 1, 75: 2 1, 76: 2 1, 77: 2 1, 78: 2 1, 79: 2 1}} > {noformat} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2318) Reimplement a Topology-Aware Consistent Hash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2318?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2318: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] from ON_QA to ON_DEV > Reimplement a Topology-Aware Consistent Hash > -------------------------------------------- > > Key: ISPN-2318 > URL: https://issues.jboss.org/browse/ISPN-2318 > Project: Infinispan > Issue Type: Task > Components: Core API, Distributed Cache > Affects Versions: 5.2.0.Alpha3 > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.Beta3 > > > Even with the advent of x-site replication, the TACH is useful to stripe key ownership across machines and/or racks for resiliency. This feature should be refactored from the 5.1 impl. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2609) Infinispan SpringCache throws java.lang.NullPointerException: Null values are not supported!

by Roland Csupor (JIRA)

Roland Csupor created ISPN-2609: ----------------------------------- Summary: Infinispan SpringCache throws java.lang.NullPointerException: Null values are not supported! Key: ISPN-2609 URL: https://issues.jboss.org/browse/ISPN-2609 Project: Infinispan Issue Type: Bug Components: Spring integration Affects Versions: 5.1.6.FINAL Reporter: Roland Csupor Assignee: Mircea Markus I trying to use Infinispan as Spring cache, but if my function returns null, I got an exception, cause Spring tries to cache this result value: {noformat} Caused by: java.lang.NullPointerException: Null values are not supported! at org.infinispan.CacheImpl.assertKeyValueNotNull(CacheImpl.java:203) ~[infinispan-core-5.1.6.FINAL.jar:5.1.6.FINAL] at org.infinispan.CacheImpl.put(CacheImpl.java:699) ~[infinispan-core-5.1.6.FINAL.jar:5.1.6.FINAL] at org.infinispan.CacheImpl.put(CacheImpl.java:694) ~[infinispan-core-5.1.6.FINAL.jar:5.1.6.FINAL] at org.infinispan.CacheSupport.put(CacheSupport.java:53) ~[infinispan-core-5.1.6.FINAL.jar:5.1.6.FINAL] at org.infinispan.spring.provider.SpringCache.put(SpringCache.java:83) ~[infinispan-spring-5.1.6.FINAL.jar:5.1.6.FINAL] at org.springframework.cache.interceptor.CacheAspectSupport.update(CacheAspectSupport.java:390) ~[spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE] at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:218) ~[spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE] at org.springframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:66) ~[spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE] {noformat} Did I misconfigured something? -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012