[JBoss JIRA] (ISPN-2629) Dist Exec testsuite fails in case of TopologyAware nodes.
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-2629?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-2629:
-------------------------------------------
Anna, lets integrate those tests as well! Where are they?
> Dist Exec testsuite fails in case of TopologyAware nodes.
> ---------------------------------------------------------
>
> Key: ISPN-2629
> URL: https://issues.jboss.org/browse/ISPN-2629
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Reporter: Anna Manukyan
> Assignee: Vladimir Blagojevic
> Fix For: 5.2.0.Beta6
>
> Attachments: DistributedExecutorWithTopologyAwareNodesTest.java, TEST-org.infinispan.distexec.DistributedExecutorWithTopologyAwareNodesTest.xml
>
>
> Many tests from dist exec test suite fail in case of TopologyAware nodes.
> It has been found that with both types of Cache configuration (old and new API), the issue appears.
> You can find the test and the stacktraces attached.
--
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
[JBoss JIRA] (ISPN-2642) IndexOutOfBoundsException in HotRodDecoder
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2642?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2642:
-----------------------------------
Fix Version/s: 5.2.0.CR1
5.2.0.Final
> IndexOutOfBoundsException in HotRodDecoder
> ------------------------------------------
>
> Key: ISPN-2642
> URL: https://issues.jboss.org/browse/ISPN-2642
> Project: Infinispan
> Issue Type: Bug
> Components: Remote protocols
> Affects Versions: 5.2.0.Beta5
> Reporter: Michal Linhard
> Assignee: Galder Zamarreño
> Fix For: 5.2.0.CR1, 5.2.0.Final
>
>
> In one of the elasticity tests in hyperion I'm getting:
> {code}
> 03:48:04,765 ERROR [org.infinispan.server.hotrod.HotRodDecoder] (HotRodClientMaster-179) ISPN005009: Unexpected error before any request parameters read: java.lang.IndexOutOfBoundsException: 2
> at scala.collection.mutable.ResizableArray$class.apply(ResizableArray.scala:44)
> at scala.collection.mutable.ArrayBuffer.apply(ArrayBuffer.scala:47)
> at org.infinispan.server.hotrod.AbstractTopologyAwareEncoder1x$$anonfun$writeHashTopologyHeader$1$$anonfun$apply$mcVI$sp$1.apply$mcVI$sp(AbstractTopologyAwareEncoder1x.scala:99) [infinispan-server-hotrod-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:81)
> at org.infinispan.server.hotrod.AbstractTopologyAwareEncoder1x$$anonfun$writeHashTopologyHeader$1.apply$mcVI$sp(AbstractTopologyAwareEncoder1x.scala:96) [infinispan-server-hotrod-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:78)
> at org.infinispan.server.hotrod.AbstractTopologyAwareEncoder1x.writeHashTopologyHeader(AbstractTopologyAwareEncoder1x.scala:93) [infinispan-server-hotrod-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.infinispan.server.hotrod.AbstractEncoder1x.writeHeader(AbstractEncoder1x.scala:62) [infinispan-server-hotrod-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.infinispan.server.hotrod.HotRodEncoder.encode(HotRodEncoder.scala:63) [infinispan-server-hotrod-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:67) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.Channels.write(Channels.java:712) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.Channels.write(Channels.java:679) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.5.9.Final.jar:]
> at org.infinispan.server.core.AbstractProtocolDecoder.writeResponse(AbstractProtocolDecoder.scala:179) [infinispan-server-core-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.infinispan.server.core.AbstractProtocolDecoder.decodeKey(AbstractProtocolDecoder.scala:115) [infinispan-server-core-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:71) [infinispan-server-core-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:47) [infinispan-server-core-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:502) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:437) [netty-3.5.9.Final.jar:]
> at org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:387) [infinispan-server-core-5.2.0.Beta5-redhat-1.jar:5.2.0.Beta5-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:84) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:472) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:333) [netty-3.5.9.Final.jar:]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35) [netty-3.5.9.Final.jar:]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> {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
[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2575:
--------------------------------
Affects Version/s: 5.2.0.Beta5
> KeyTransformer registration is required on all nodes of the cluster, in case of custom keys
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-2575
> URL: https://issues.jboss.org/browse/ISPN-2575
> Project: Infinispan
> Issue Type: Feature Request
> Components: Querying
> Affects Versions: 5.2.0.Beta5
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Fix For: 5.2.0.CR1
>
> Attachments: ClusteredCacheTest.java
>
>
> The case is the following:
> I have a clustered cache on which I want to perform a search. I'm doing the following:
> I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception:
> java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer
> When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager.
> The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer()
--
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
[JBoss JIRA] (ISPN-2581) StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2581?page=com.atlassian.jira.plugin.... ]
Work on ISPN-2581 started by Adrian Nistor.
> StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon
> ---------------------------------------------------------------------------------
>
> Key: ISPN-2581
> URL: https://issues.jboss.org/browse/ISPN-2581
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.Beta5
> Reporter: Dan Berindei
> Assignee: Adrian Nistor
> Priority: Critical
> Fix For: 5.2.0.CR1
>
>
> StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns as soon as a joining node confirmed to the coordinator that it received all the data it needed (see STMI.notifyEndOfTopologyUpdate()).
> It should return only after the coordinator has confirmed the end of the rebalance with a new topology update (see STMI.doTopologyUpdate()).
> This should make it more likely for the tests suite clusters to be in a stable state by the time the test starts, and should help with the random state transfer-related failures in non-state transfer tests.
> Instead we should make sure that we do have tests that check forwarding behaviour explicitly.
--
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
[JBoss JIRA] (ISPN-2584) BackupReceiver survives cache shutdown
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2584?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2584:
--------------------------------
Fix Version/s: 5.2.0.CR1
> BackupReceiver survives cache shutdown
> --------------------------------------
>
> Key: ISPN-2584
> URL: https://issues.jboss.org/browse/ISPN-2584
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 5.2.0.Beta5
> Reporter: Radim Vansa
> Assignee: Mircea Markus
> Fix For: 5.2.0.CR1
>
>
> When the cache manager is stopped together with all caches, the static field {{BackupReceiverRepositoryImpl.backupReceivers}} is not cleaned up. When another cache manager is started and we try to XS replicate into this node, the request reaches {{BackupReceiver}} with references to the old, stopped cache. This instance has TERMINATED ComponentRepository without {{TransactionTable}} and this results in {{NullPointerException}} in {{BackupCacheUpdater.replayModificationsInTransaction}}.
> When the cache is stopped, it should remove all references to it from the {{BackupReceiverRepositoryImpl.backupReceivers}}.
--
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