December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2631) HotRod server attempts to cast to CacheImpl

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2631?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2631: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1525 > HotRod server attempts to cast to CacheImpl > ------------------------------------------- > > Key: ISPN-2631 > URL: https://issues.jboss.org/browse/ISPN-2631 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > The HotRod server attempts to cast an AdvancedCache to CacheImpl directly which is wrong (and incidentally breaks JDG) > The getCacheEntry() method should be exposed on the AdvancedCache interface -- 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-2631) HotRod server attempts to cast to CacheImpl

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2631?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-2631: --------------------------------------- P.S. It was all my fault > HotRod server attempts to cast to CacheImpl > ------------------------------------------- > > Key: ISPN-2631 > URL: https://issues.jboss.org/browse/ISPN-2631 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > The HotRod server attempts to cast an AdvancedCache to CacheImpl directly which is wrong (and incidentally breaks JDG) > The getCacheEntry() method should be exposed on the AdvancedCache interface -- 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-2631) HotRod server attempts to cast to CacheImpl

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2631: ------------------------------------- Summary: HotRod server attempts to cast to CacheImpl Key: ISPN-2631 URL: https://issues.jboss.org/browse/ISPN-2631 Project: Infinispan Issue Type: Enhancement Components: Remote protocols Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Blocker Fix For: 5.2.0.Beta6 The HotRod server attempts to cast an AdvancedCache to CacheImpl directly which is wrong (and incidentally breaks JDG) The getCacheEntry() method should be exposed on the AdvancedCache interface -- 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-2352) Second invocation of ClusteredQueryImpl.lazyIterator() yields results in reverse order

by Marko Lukša (JIRA)

[ https://issues.jboss.org/browse/ISPN-2352?page=com.atlassian.jira.plugin.... ] Marko Lukša commented on ISPN-2352: ----------------------------------- If I remember correctly, this bug was just something I noticed when I was changing the Query result iterators in Infinispan. So I don't actually have anything in CapeDwarf that would be affected by this (we always create a fresh query instance - we never call iterator() twice on the same instance). > Second invocation of ClusteredQueryImpl.lazyIterator() yields results in reverse order > -------------------------------------------------------------------------------------- > > Key: ISPN-2352 > URL: https://issues.jboss.org/browse/ISPN-2352 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.1.8.Final, 5.2.0.Alpha4 > Reporter: Marko Lukša > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 5.2.0.Beta6, 5.2.0.Final > > > When you invoke lazyIterator() for the 2nd time on the same ClusteredQueryImpl instance, the iterator returns results in reverse order. This only occurs when the query has a Sort specified. > Caused by DistributedIterator.setTopDocs(), which inverts the reverse flag on SortField. > The same is probably also true for ClusteredQueryImpl.iterator() -- 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-2630) CacheLoader searching/disabling should also take into account delegating cachestores (async+singleton)

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2630: ------------------------------------- Summary: CacheLoader searching/disabling should also take into account delegating cachestores (async+singleton) Key: ISPN-2630 URL: https://issues.jboss.org/browse/ISPN-2630 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Critical Fix For: 5.2.0.CR1 -- 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-2629) Dist Exec testsuite fails in case of TopologyAware nodes.

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2629?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2629: -------------------------------- Description: 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. was: Many tests from dist exec test suite fails 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. > 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 > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2629) Dist Exec testsuite fails in case of TopologyAware nodes.

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2629?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2629: -------------------------------- Attachment: DistributedExecutorWithTopologyAwareNodesTest.java > 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 > Attachments: DistributedExecutorWithTopologyAwareNodesTest.java, TEST-org.infinispan.distexec.DistributedExecutorWithTopologyAwareNodesTest.xml > > > Many tests from dist exec test suite fails 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2629) Dist Exec testsuite fails in case of TopologyAware nodes.

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2629?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2629: -------------------------------- Attachment: TEST-org.infinispan.distexec.DistributedExecutorWithTopologyAwareNodesTest.xml > 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 > Attachments: DistributedExecutorWithTopologyAwareNodesTest.java, TEST-org.infinispan.distexec.DistributedExecutorWithTopologyAwareNodesTest.xml > > > Many tests from dist exec test suite fails 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2629) Dist Exec testsuite fails in case of TopologyAware nodes.

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2629: ----------------------------------- Summary: 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 Many tests from dist exec test suite fails 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2550) NoSuchElementException in Hot Rod Encoder

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2550?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2550: ---------------------------------------- Tomas' functional issue has now been separated into ISPN-2624, leaving this JIRA fully focused on the situation when the nodes are killed. > NoSuchElementException in Hot Rod Encoder > ----------------------------------------- > > Key: ISPN-2550 > URL: https://issues.jboss.org/browse/ISPN-2550 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta4 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > Tomas noticed this a while ago in a specific functional test: > https://bugzilla.redhat.com/show_bug.cgi?id=875151 > I'm creating a more general JIRA, cause I'm having this in resilience test. > What I found by quick debug, is that here: > https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/ma... > {code} > for (segmentIdx <- 0 until numSegments) { > val denormalizedSegmentHashIds = allDenormalizedHashIds(segmentIdx) > val segmentOwners = ch.locateOwnersForSegment(segmentIdx) > for (ownerIdx <- 0 until segmentOwners.length) { > val address = segmentOwners(ownerIdx % segmentOwners.size) > val serverAddress = members(address) > val hashId = denormalizedSegmentHashIds(ownerIdx) > log.tracef("Writing hash id %d for %s:%s", hashId, serverAddress.host, serverAddress.port) > writeString(serverAddress.host, buf) > writeUnsignedShort(serverAddress.port, buf) > buf.writeInt(hashId) > } > } > {code} > we're trying to obtain serverAddress for nonexistent address and NoSuchElementException is not handled properly. > It hapens after I kill a node in a resilience test and the exception appears when querying for the node in the members cache. -- 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